fix(route53): warn when ttl is provided with alias target in RecordSet

[gasolima]

Issue # (if applicable)

N/A

Reason for this change

When creating a Route53 RecordSet with an alias target, the ttl property is ignored since alias targets don't use TTL values.

Description of changes

This change adds a warning annotation to inform users when they provide a ttl value that will be ignored. This improves developer experience by making it clear when a provided configuration option has no effect, helping users avoid confusion and potential misconfigurations.

Describe any new or updated permissions being added

N/A

Description of how you validated changes

Created a resource that triggers the warning as shown below, then linked my PR changes and ran $ cdk synth

    new ARecord(this, 'ARecord', {
      zone: hostedZone,
      recordName: 'api.dev.mydemo-domain-abc.net',
      target: RecordTarget.fromAlias( 
        new LoadBalancerTarget(alb),
      ),
      ttl: cdk.Duration.seconds(15),
      deleteExisting: true,
    });

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)

[matboros]

Please add unit tests for your change

✅ 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).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: d64803b
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[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.