This PR introduces a new community module community/modules/scripts/gcloud that allows developers to run
arbitrary gcloud commands as part of their Cluster Toolkit deployments.

Motivation:

There are scenarios where direct gcloud execution is necessary within a blueprint:

1. Rapidly Use New Features: To leverage new GCP features or services that are available in gcloud but not
   yet fully supported in the Terraform provider or integrated into Cluster Toolkit core modules.
2. Bridge Feature Gaps: To perform specific actions or configurations that are easier or currently only
   possible via the gcloud CLI.

This module provides a flexible way to handle these cases, particularly useful for proofs of concept and
early adoption of features, while more permanent Terraform-based solutions can be developed.

Implementation:

• The module takes a list of objects, each containing a create and a delete command.
• It uses local-exec provisioners within a null_resource to run the commands.
• Create commands are run in the order provided.
• Delete commands are run in the reverse order during the destroy lifecycle.
• The module ID is injected via metadata.yaml to ensure proper context.
• Create/Destroy scripts are generated in the locals block and stored in resource triggers to work within
  Terraform's destroy-time provisioner limitations.

Example:

An example blueprint community/examples/gcloud-example.yaml is included, demonstrating the creation and
deletion of a VPC, subnet, and VM instance using the new module.

Limitations:

• This module does not produce Terraform outputs. Dependencies on resources created by this module must be
  managed by placing this module in an earlier deployment_group.
• Idempotency relies on the idempotency of the provided gcloud commands.

This module offers increased flexibility for users needing to integrate gcloud workflows directly into their
Cluster Toolkit deployments.