resource/gitlab_project: Fix passing `ci_forward_deployment_enabled=false` at project creation

Description

Gitlab API only allows updating ci_forward_deployment_enabled when editing a project. Setting ci_forward_deployment_enabled=false at project creation has no effect. We need to terraform apply twice the apply the change.

Related Gitlab issues:

• gitlab#341672
• gitlab!44510 (merged)

This MR add ci_forward_deployment_enabled to editProjectOptions to update the parameter after the creation.

PR Checklist Acknowledgement

• I acknowledge that all of the following items are true, where applicable:
  • Resource attributes match 1:1 the names and structure of the API resource in the GitLab API documentation.
  • Examples are updated with:
    • A *.tf file for the resource/s with at least one usage example
    • A *.sh file for the resource/s with an import example (if applicable)
  • New resources have at minimum a basic test with three steps:
    • Create the resource
    • Update the attributes
    • Import the resource
  • No new //lintignore comments were copied from existing code. (Linter rules are meant to be enforced on new code.)