gcp : add alloydb group

[jcockbain]

Description of your changes

Fixes #371

Adds resources for:

google_alloydb_backup
google_alloydb_instance
google_alloydb_cluster

I have:

• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

I deployed instances of the 3 new kinds to to a minikube cluster. These were based on the generated examples, adapted for my test GCP project.

I then used make run, which created the expected resources in my project.

Each of these resource became "ready". Deleting the k8s resources deletes the resources from GCP.

Cluster: https://github.com/upbound/provider-gcp/actions/runs/6110391551

Instance:

Backup:

[Upbound-CLA]

All committers have signed the CLA.

[turkenf]

/test-examples="examples/alloydb/instance.yaml"

[jcockbain]

@turkenf are you able to assist with the failure on ci/check-diff? Running make check-diff from my workstation passes fine.

[turkenf]

Hi @jcockbain,

After running make generate there seem to be changes you didn't commit, can you run make generate again and commit all the changes?

[jcockbain]

@turkenf thanks. I have updated my branch, and changed the commits to show the manual and then the generated changes. make generate does not create any new files on my branch now, so hopefully the CI will be okay.

[jcockbain]

Hi @turkenf, I run make generate on my machine and it passes fine - but the CI job is still failing. Any advice on what I could be missing here?

[turkenf]

@jcockbain, could you please rebase your branch to the main, run make generate, and commit all the changes again?

[jcockbain]

Thanks @turkenf, there were extra files generated after rebasing.

[turkenf]

@jcockbain, many thanks for your contribution. I left a few comments for you to consider.

Could you please fill in how it was tested after the last changes for each resource as here?

[jcockbain]

Thanks very much for your comments @turkenf, I have attempted to resolve them all in the above commit.

I also retested with the examples and added screenshots to the summary of this PR.

[jcockbain]

One thing I am not certain on is what to name example resources, for my testing I gave the resources different names as default is already used for some of the resources in my test project. So I left these test names in the example manifests, but I can change them back to the generated ones if that would be better.

[turkenf]

Thank you for the quick update @jcockbain, the names look good for now, they can stay that way. I just left two minor comments that fix the example-ids.

[turkenf]

/test-examples="examples/alloydb/cluster.yaml"

[turkenf]

/test-examples="examples/alloydb/cluster.yaml"

[turkenf]

@jcockbain, Thank you again for your contribution and clean work. LGTM.