feat(custom-resource): upgrade to python runtime 3.13 for custom resources

[abidhasan-aws]

Reason for this change

• Current custom resource handlers are using Python 3.9 and 3.11 runtimes
• Python 3.9 reaches EOL in October 2025
• Need to upgrade to Python 3.13 for better stability and continued support
• Affects multiple custom resource handlers including aws-ecs/drain-hook-provider, aws-eks/kubectl-provider, and others

Description of changes

• Updated Python runtime from 3.9/3.11 to 3.13 in config.ts for generated bundle functions
• Modified runtime settings in:
  • notifications-resource-handler.ts
  • instance-drain-hook.ts
• Updated aws-eks-v2-alpha custom resource handler runtime
• Updated integration tests and snapshots

Validation

• Deployed integration tests across multiple regions to verify functionality
• Verified Lambda Python 3.13 availability across required regions

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[aws-cdk-automation]

(This review is outdated)

[aemada-aws]

title should be feat(custom-resource)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request manually updated.

The pull request #35342 has been manually updated.

If you want to requeue this pull request, you can post a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.