fix(lambda): lambda does not set environment variables for AWS_CODEGURU_PROFILER properties when creating Amazon CodeGuruProfiler profiling group

[ConnorRobertson]

Issue

When { profiling: true } CDK creates a profiling group using autogenerated parameters which is never set as an environment variable. This causes another profiling group with default parameters to be created by the lambda. This can create permissions issues. This is an issue when the Lambda has Java or Python runtime but not other runtimes.

Solution

For the python, corretto and jdk11 runtime, they will not look at
AWS_CODEGURU_PROFILER_GROUP_ARN and will only look at
AWS_CODEGURU_PROFILER_GROUP_NAME and AWS_CODEGURU_PROFILER_TARGET_REGION. Runtimes that support AWS_CODEGURU_PROFILER_GROUP_ARN prefer AWS_CODEGURU_PROFILER_GROUP_NAME and AWS_CODEGURU_PROFILER_TARGET_REGION and fallback onto the ARN.
So the solution sets these values as potential environment variables.

Important Design Decisions

I changed profiling validation to not error and instead warn the user to have environment variables remain consistent with each other while having no backwards compatibility concerns.

Remember to follow the CONTRIBUTING GUIDE and DESIGN GUIDELINES for any
code you submit.

Closes #23511 .

---

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

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 11747ea
• 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).