Support AlloyDBInstance type, mapper and direct controller

[maqiuyujoyce]

Change description

Supported AlloyDBInstance type, mapper and direct controller

• Changes in the AlloyDBInstance CRDs are non-breaking. Mostly caused by the format of the field descriptions and how we generate direct CRDs.
• Added "direct" annotation to all the AlloyDBInstance in the alloydbinstance test cases.
• Updated the AlloyDBInstance in the test cases to use the direct controller instead.
  • The golden files are updated based on the behavior of the direct controller, which are all expected. Note that the TF-based controller somehow does an additional reconciliation right after the successful creation. The direct reconciliation doesn't do it, which caused one less GET event. Another thing is that the EnsureFinalizer() step in TF-based reconciliation possibly increased the generation by one during reconciliation, so the generation value is different. Overall the values and behaviors look more reasonable in the direct controller test result.

Tests you have done

• Run make ready-pr to ensure this PR is ready for review.
• Perform necessary E2E testing for changed resources.

Logs when running against the real GCP using the direct controller: #3361 Note that the dependent resources are all abandoned to save test time so please ignore the diffs unrelated to AlloyDBInstance.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from maqiuyujoyce. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment