[Bug] Use subnet hash to create a new target group if subnetID is updated

[himani2411]

Description of changes

• Include subnet hash in both the logical ID and target group name to force replacement when subnet changes.
  This avoids two errors during cluster update when subnet changes:
  1. "target group cannot be associated with more than one load balancer" - solved by new logical ID
  2. "target group name already exists" - solved by new target group name
     Both must change because CloudFormation creates the new resource BEFORE deleting the old one and target group names must be unique within a region/account.

Tests

• Unit Test
• Manual Test where I create a cluster with subnet_A and update a cluster with subnet_B when the login Node pool is 0

References

• Link to impacted open issues.
• Link to related PRs in other packages (i.e. cookbook, node).
• Link to documentation useful to understand the changes.

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

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

[hehe7318]

LGTM. Please address the minor format issue.

But the unit tests seems failed. Can you check?

[himani2411]

Taking a look at the failures in code-linters