fix(logger): allow custom JMESPath functions to extract correlation ID

[heitorlessa]

Issue number: #3381

Summary

This 3-year bug prevented customers from using custom JMESPath Functions like powertools_json to deserialize and extract correlation ID more easily.

Changes

Please provide a summary of what's being changed

• Use jmespath_utils instead of jmespath.search
• Briefly mention that custom jmespath functions work in Docs
• Add missing test

User experience

Please share what the user experience looks like before and after this change

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.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
3.3% Duplication