feat(sns): add TracingConfig prop

[jun1-t]

Issue # (if applicable)

Closes #29714

Reason for this change

Currently, to set the TracingConfig, it is necessary to configure it via L1.
So, add TracingConfig props to L2.

Description of changes

added TracingConfig props to topic.ts, sns.test.ts, integ.sns.ts, and README.md for AWS SNS.

Description of how you validated changes

I confirmed with unit test and integ test that it works as expected.

---

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

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

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

[nmussy]

Previously reviewed in #29715, still LGTM 👍

[TheRealAmazonKendra]

Thank you for your contribution! Excellent feedback here from @nmussy so I have nothing further.

For future reference, maintainers can reopen closed PRs regardless of who closes them so feel free to tag one of us and we can help reopen the original one, if that's easier for you.

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

[jun1-t]

@TheRealAmazonKendra @nmussy
Thank you for the approval. And, thank you for letting me know about reopening the pull request. I understand.

However, it appears that the subsequent check failed. The details of the error that occurred during the check, it is written as follows, but I'm unsure what specific actions to take. What should I do?

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/request-cli-integ-test.yml without workflows permission

[nmussy]

You should have a checkbox on the right side of this page, which needs to be selected, "Allow edits and access to secrets by maintainers"

Once it's done, you can send the message @mergifyio update to force it to refresh and merge

[jun1-t]

@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/request-cli-integ-test.yml without workflows permission

[nmussy]

This might be an issue with mergify, I'll let a maintainer take over

[jun1-t]

@nmussy

This might be an issue with mergify, I'll let a maintainer take over

Thank you for letting me know. I understand.
It looks slightly different from nmussy's image, but the checkbox appears to be selected.

Pull request has been modified.

[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: e4c12e5
• 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).

[jun1-t]

@xazhao
Thank you for merging.

[aws-cdk-automation]

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.