Dependabot PR #59 needs manual terraform provider investigation

[ben-vaughan-nttd]

Context

Dependabot PR #59 attempted a major terraform provider version bump that failed CI.
An automated fix was attempted:

1. Rebased the PR branch onto the base branch
2. Added ignore rules to .github/dependabot.yml for major version bumps of hashicorp/*, microsoft/*, azure/*
3. Reverted versions.tf to the base branch version

CI still failed after the fix, which means there may be additional issues beyond the major version bump.

What to investigate

• Check the CI logs for the specific failure: https://github.com/launchbynttdata/tf-aws-module_primitive-lambda_layer/actions/runs/23909322138/job/69726778490
• The dependabot config change (ignore rules) is likely still valid and should be kept
• There may be minor/patch version incompatibilities or other dependency conflicts
• Note: this was a grouped PR (Bump the "module" group with 2 updates across multiple ecosystems) that included go module updates alongside the terraform provider bump -- the go module changes may be the cause of the failure
• Review whether the terraform module needs code changes to support newer provider versions

Suggestion

Consider manually creating a PR that just adds the dependabot ignore rules (without the go module updates) to prevent future major version bump PRs from being created.

PR reference

• Original PR: Bump the "module" group with 2 updates across multiple ecosystems #59
• PR title: Bump the "module" group with 2 updates across multiple ecosystems