chore(integ-test-alpha): add log group retention days to integ test stack

[GavinZZ]

Issue # (if applicable)

Closes #29260

Reason for this change

CloudWatch log groups created by the integ tests are set to never expire, so end up cluttering up your aws account and need manual cleanup.

Description of changes

Added custom log group with log group retention

Description of how you validated changes

All existing tests and new tests pass.

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

[TheRealAmazonKendra]

I would prefer that we make this a configurable field rather than just assigning an arbitrary time period.

[paulhcsun]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

Dismissing as the feedback is addressed

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

[mokele]

This PR has a bug that if you use this feature then you cannot have more than 1 long running assertion stack co-exist in the same aws account.

It's common to have shared aws accounts, and this feature uses the hardcoded singleton uuid value with id then used for the log group /aws/logs/{id}, making it the same across the whole account not just the current stack, making it not possible to have multiple longer running assertion stacks (with --no-clean).

I'm not sure yet if there is a way to circumvent this and get to override the uuid that is baked in here that results in part of the singleton functions's id 😢

I'll work on writing up a proper bug issue when I have a moment