feat: Scope KMS auth policy to the exact KMS key

[arya-girish-k]

Description

Scope KMS Auth poicy to the exact KMS key.
Git Issue

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

This PR is to scope he KMS Auth policy to the exact KMS key.

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[arya-girish-k]

/run pipeline

[arya-girish-k]

/run pipeline

[arya-girish-k]

Added variable kms_encryption_enabled in DA.Hence Re-triggerring the pipeline

[arya-girish-k]

/run pipeline

[arya-girish-k]

As per the document authorization policy gets created at Instance level.
Currently while scoping KMS policy to the exact KMS key ,policy gets created but provisioning of secret manager instance is failing .As per the discussion scoping authorization policy at key level is not allowed
Hence closing the PR.