feat(core): addInfoV2 method for suppressible info Annotations

[hassaku63]

Issue # (if applicable)

Closes #34871

Reason for this change

This feature request proposes add Annotations.addInfoV2() method to provide CDK developers the way to suppressable info message. This allows the CDK users to suppress the unnecessary info annotation message.

I propose adding addInfoV2() -- the Info-level counterpart to addWarningV2() -- which would let builders acknowledge an Info message once and prevent it from re-appearing in subsequent runs.

Description of changes

This PR adds the following new features to the Annotations class:

1. addInfoV2 method - A method to add acknowledgeable info messages
2. acknowledgeInfo method - A method to mark specific info messages as acknowledged

These changes follow the same pattern as the existing warning message functionality (addWarningV2/acknowledgeWarning), maintaining API consistency.

Describe any new or updated permissions being added

This PR does not add any new IAM permissions.

Description of how you validated changes

The following tests were added to validate the functionality:

1. Tests confirming that addInfoV2 correctly adds info messages
2. Tests verifying that acknowledgeInfo correctly marks info messages as acknowledged and they are no longer displayed

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)

[hassaku63]

Exemption request for integration test / snapshot requirement

This change only adds functionality inside the core package’s Annotations class.

• There is currently no existing integration test file that targets Annotations
• An integ test just to hit addInfoV2() would add boilerplate without meaningful new coverage—the unit test already verifies the method’s behavior.

Given that Annotations operates entirely within the core library and does not affect synthesized templates directly, I believe an integration test is unnecessary in this case.

[badmintoncryer]

I've compared it with the existing addWarningV2 method implementation, and I think it looks good to me.

✅ 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 branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mrgrain]

@Mergifyio update

[mergify]

update

❌ Mergify doesn't have permission to update

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/codecov-upload.yml without workflows permission

Pull request has been modified.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 539fa6d
• 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.