Add support for restoring AlloyDB clusters via backup restore and PITR

[modular-magician]

Add support for restoring AlloyDB clusters via backup restore and PITR.

To restore a cluster directly from a backup, add the following line to your AlloyDB cluster:

restore_backup_source {
  backup_name = <fully qualified backup name>
}

To restore a cluster via PITR, add the following lines to your AlloyDB cluster:

restore_continuous_backup_source {
  cluster = <fully qualified source cluster name>
  point_in_time = <timestamp in RFC 3339 format>
}

Part of #13757. I am not fully closing the issue because I did not yet add support for data calls for backups as requested.

If this PR is for Terraform, I acknowledge that I have:

• Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).
• Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).
• Generated Terraform providers, and ran make test and make lint in the generated providers to ensure it passes unit and linter tests.
• Ran relevant acceptance tests using my own Google Cloud project and credentials (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
• Read Write release notes before writing my release note below.

Release Note Template for Downstream PRs (will be copied)

alloydb: added `restore_backup_source` and `restore_continuous_backup_source` fields to support restore feature in `google_alloydb_cluster` resource.

Derived from GoogleCloudPlatform/magic-modules#8575

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.