Fix nested secrets and names conversion

[visit1985]

Issue #, if available:

This PR is related to aws-controllers-k8s/community#2813.

During my attempt to generate the ack-dms-controller, I identified the following problems:

• Nested secret fields with acronyms (e.g., SASLPassword, SSLClientKeyPassword) could not be found in MemberFields map because the lookup used raw AWS SDK names (SaslPassword, SslClientKeyPassword) while the map is keyed by normalized camelCase names.
• Secret field setters for nested struct members were not being automatically suppressed based on the is_secret: true configuration.

Description of changes:

• All secret fields (top-level and nested) marked with is_secret: true automatically suppress SDK→CRD output setters.
• Field config lookups are now consistently case-insensitive across all code paths.
• Acronym normalization (e.g., Sasl → SASL) no longer causes member field lookup failures.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ack-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: visit1985
Once this PR has been reviewed and has the lgtm label, please assign michaelhtm for approval by writing /assign @michaelhtm in a comment. For more information see the Kubernetes Code Review Process.

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

Details

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

[ack-prow]

Hi @visit1985. Thanks for your PR.

I'm waiting for a aws-controllers-k8s member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.