docs(logger): clarify Advanced Logging Controls interaction with sampling

[kattakaha]

Issue number: closes #7220

Summary

Changes

This PR addresses documentation improvements for AWS Lambda Advanced Logging Controls (ALC) interaction with Powertools Logger sampling functionality. The changes clarify how Lambda's log level settings override Powertools configuration and provide clear guidance to avoid confusion.

Based on review feedback from @leandrodamascena in PR #7412:

• Enhanced CDK example wording to be more precise about Lambda setting the environment variable
• Added ALC reference in sampling introduction section instead of separate warning block to avoid page clutter
• Maintained clear priority order examples showing how Lambda's log level takes precedence

User experience

Before: Users were confused about the interaction between Lambda's Advanced Logging Controls and Powertools sampling settings, leading to unexpected behavior where sampling didn't work as expected when ALC was set to DEBUG level.

After: Users have clear documentation explaining:

• How Lambda's log level settings override Powertools configuration
• Why sampling may not work when ALC is set to DEBUG
• How CDK's applicationLogLevelV2 automatically sets AWS_LAMBDA_LOG_LEVEL
• The priority order of log level settings with concrete examples

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[Copilot]

Pull Request Overview

This PR improves documentation clarity around AWS Lambda Advanced Logging Controls (ALC) interaction with Powertools Logger sampling functionality. The changes address user confusion about when Lambda's log level settings override Powertools configuration, potentially causing unexpected sampling behavior.

Key changes:

• Added detailed explanation of CDK applicationLogLevelV2 parameter behavior in log level priority section
• Added reference to ALC interaction within the sampling introduction section
• Clarified how Lambda automatically sets AWS_LAMBDA_LOG_LEVEL environment variable

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[leandrodamascena]

Hey @kattakaha! Can you please only incorporate this small change and then we merge?

dfc8509#diff-e42af4aee30a146e6e51be432c4a80c93e50d552f7b70403fa301ecf11d355c4R378

[kattakaha]

@leandrodamascena Sorry for missing that change in the new PR! I've now added the broken ALC documentation link fix as requested. Thanks for your patience with the multiple iterations.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[leandrodamascena]

Thanks for working on this @kattakaha! APPROVED!