feat(general): make logger, tracer and metrics utilities aware of provisioned concurrency

[leandrodamascena]

Issue number: #6321

Summary

Changes

This PR improves cold start detection in AWS Powertools for Python by leveraging the AWS_LAMBDA_INITIALIZATION_TYPE environment variable to accurately identify function initialization states across Provisioned Concurrency (PC) environments.

There are some considerations in this PR:

• We currently rely on a global variable when importing a specific module, which creates challenges for cold start detection across modules. To address this properly, we would need to refactor the code to use a single function that can control cold start logic across all modules. However, this would involve significant work and I'd need to invest too much time seeing the impact. To avoid this risk, I will temporarily duplicate code across modules to ensure compatibility and prevent disruptions.

• The cold start detection logic for Metrics is even more problematic because it relies on legacy code that has been in place since Powertools was first released. In the [feat(metrics): support to bring your own metrics provider #2194], we attempted to refactor this logic but realized that customers are directly importing certain variables, and changing them could break existing implementations. As a result, adding tests for Metrics (specific for PC) would require a major refactor, which I don't want to undertake at this time. For now, I will maintain the current implementation to avoid introducing risks while ensuring stability for customers.

• I'm happy to move forward with this PR, even with these limitations.

• I'm adding a new item to the v4 discussion to track these items

User experience

Doesn't change the customer experience.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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.

[codecov]

Codecov Report

Attention: Patch coverage is 91.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 96.31%. Comparing base (52a2ade) to head (d4f23e0).
Report is 2 commits behind head on develop.

Files with missing lines	Patch %	Lines
...s_lambda_powertools/metrics/provider/cold_start.py	60.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6324      +/-   ##
===========================================
- Coverage    96.32%   96.31%   -0.02%     
===========================================
  Files          242      242              
  Lines        11689    11706      +17     
  Branches       867      870       +3     
===========================================
+ Hits         11260    11275      +15     
- Misses         336      337       +1     
- Partials        93       94       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leandrodamascena]

Hey @dreamorosi! I'd like your review here. Please read the PR body.

[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

[dreamorosi]

Agree with the overall strategy of postponing the major refactor, I only have a question about the actual logic before we move forward.

After we've clarified that I can approve

[leandrodamascena]

Agree with the overall strategy of postponing the major refactor, I only have a question about the actual logic before we move forward.

After we've clarified that I can approve

Already replied that. Please let me know if you have any additional question.