feat(jmespath): add parser component

[dreamorosi]

Description of your changes

This PR introduces the Parser component to the JMESPath utility.

The parser is the main orchestrator component and uses a lexer (#2205), AST (#2210), and tree interpreter (#2209) to tokenize, abstract, and traverse the JMESPath expression and produce a result.

Related issues, RFCs

Issue number: #2211

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

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.

[dreamorosi]

The tests that will cover this and all other JMESPath PRs are in this PR: #2271

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud