CCM-9743: disable amplify auto disconnect

[bhansell1]

Description

• disables Amplify's branch auto disconnect

Context

pr_close workflows are failing, this failure. Happens because we're explicitly stating we want to delete the branch, but it has already been deleted due to the auto disconnect policy.

We're favouring using TF resource remove_amplify_branch instead of Amplify's branch auto disconnect

Disabling auto branch disconnect will still clean up Amplify branches on PR close. The pr_destroy_dynamic_env.yaml workflow is triggered on PR closed which will perform a tf destroy, which calls remove_amplify_branch.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.