[GCP] | Enforce independent resource provisioning per environment

[mk-armah]

Issue:
When executing terraform apply with project feeds that already exist within the GCP account, Terraform fails and returns an error stating that the feed already exists.

Solution:
To prevent such errors and enhance support for multi deployments, We Introduce an extra variable environment that prefixes the resources identifiers, enforcing unique identifier per deployment and preventing the duplication error.

Changes Include:

• Enhanced support for multi deployment setups by adding an extra variable environment. (e.g stg, prod)`
• Updated default naming convention to utilize the given integration_name and environment.
  e.g my-gcp-integration-prod, my-gcp-integration-stg,my-gcp-integration-dev

Benefits:

• Prevents Terraform from failing due to duplicate feed errors.
• Allows for smoother integration with pre-existing GCP asset feeds.
• Easy identification of integration resources due to the consistent naming convention between Port and GCP integration

Testing:
Verified that terraform apply successfully skips the creation of existing feeds and applies changes without errors.