Mark Alloydb instance database_flags as default_from_api

[modular-magician]

Marking the database_flags field in the alloydb instance resource to be default_from_api
This is needed to reflect the actual database_flags for secondary instance, as the database_flags are copied from primary instance to secondary instance during secondary instance creation.

If the database_flags is not set for secondary instance, it successfully copies the flags during the creation phase.
However, with any further terraform apply command, it believes that the database_flags needs to be removed as the config doesn't have the database_flags field and performs an update operation instead.

Marking default_from_api for the field to true ensures that this doesn't happen

Release Note Template for Downstream PRs (will be copied)

alloydb: fixed an issue where `database_flags` in secondary `google_alloydb_instance` resources would cause a diff, as they are copied from the primary

Derived from GoogleCloudPlatform/magic-modules#9868

[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.