Roll out tag bindings to all supported resources

[juliocc]

[see below comment for details]

[ludoo]

We should support most of the services/resources listed here, excluding those in alpha (which are quite a few).

• alloydb
• bigquery
• bigtable
• cloud-run
• coud-run-v2
• gcs
• kms

The compute resources (forwarding rules, disks, etc.) need to expose the generated (numeric) id which is not currently available everywhere (backend services have it, forwarding rules and disks don't, etc.). An FR needs to be opened on the provider to implement exhaustive support for generated ids on all relevant resources before tag bindings can be implemented. For instance support, see the comment in the compute-vm module.

[ludoo]

@simonebruzzechesse can you implement support for alloydb? I know you're testing it for a customer so you might have instances up already, which I don't have.

[ludoo]

Closing this while Julio figures out if it's worth adding support for numeric ids to compute resources. Alloydb and bigtable will be done if/when there's a need for them, no point keeping this issue open.