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

Author: kattakaha

docs/core/logger.md

@@ -409,6 +409,11 @@ We prioritise log level settings in this order:
 2. Explicit log level in `Logger` constructor, or by calling the `logger.setLevel()` method
 3. `POWERTOOLS_LOG_LEVEL` environment variable
 
+!!! info "AWS CDK and Advanced Logging Controls"
+    When using AWS CDK's `applicationLogLevelV2` parameter or setting log levels through the Lambda console, AWS Lambda automatically sets the `AWS_LAMBDA_LOG_LEVEL` environment variable. This means Lambda's log level takes precedence over Powertools for AWS configuration, potentially overriding both `POWERTOOLS_LOG_LEVEL` and sampling settings.
+
+    **Example**: If you set `applicationLogLevelV2=DEBUG` in CDK while having `POWERTOOLS_LOG_LEVEL=INFO`, the DEBUG level will be used because Lambda automatically sets the environment variable `AWS_LAMBDA_LOG_LEVEL` to the debug level.
+
 If you set `Logger` level lower than ALC, we will emit a warning informing you that your messages will be discarded by Lambda.
 
 > **NOTE**
@@ -825,6 +830,8 @@ Use sampling when you want to dynamically change your log level to **DEBUG** bas
 
 You can use values ranging from `0.0` to `1` (100%) when setting `POWERTOOLS_LOGGER_SAMPLE_RATE` env var, or `sampling_rate` parameter in Logger.
 
+**AWS Lambda Advanced Logging Controls (ALC)** settings can affect Sampling behavior. See [how it works](#aws-lambda-advanced-logging-controls-alc).
+
 ???+ tip "Tip: When is this useful?"
     Log sampling allows you to capture debug information for a fraction of your requests, helping you diagnose rare or intermittent issues without increasing the overall verbosity of your logs.