[SFN] Support for JsonPath Regexes

[MEPalma]

Motivation

Currently the SFN v2 provider incorrectly parses json path strings especially when filtering options. Furthermore, the non extended version of jsonpath_ng parser is used. The PR simplified the parsing of json path definitions and delegates them all as a complete string to jsonpath_ng. The PR also resolves some issue with returning single objects or list of objects in some json path accesses.
However, currently, the jsonpath_ng is not always able to adhere to spec h2non/jsonpath-ng#8. This issue should be followed in the future, and the tests added in this PR enabled for filtering json path definitions. Addresses and stales: #9937

Changes

• updated the intrinsic lexer and parser to bind any json path definition to a single token
• updated the json path access logic to use jsonpath_ng ext parser
• updated the json path access logic to more consistently return single objects or list of objects depending on the json path definition
• adds relevant tests

[github-actions]

LocalStack Community integration with Pro

    2 files  ±0      2 suites  ±0   1h 26m 41s ⏱️ + 5m 7s
2 644 tests +2  2 396 ✅ +1  248 💤 +1  0 ❌ ±0 
2 646 runs  +2  2 396 ✅ +1  250 💤 +1  0 ❌ ±0 

Results for commit 46a654e. ± Comparison against base commit b558f3a.

♻️ This comment has been updated with latest results.

[coveralls]

coverage: 83.857% (-0.008%) from 83.865%
when pulling 46a654e on MEP-sfn-jsonpath-regex
into b558f3a on master.

[phildunphytoo]

I would love to see this merged :)

[dominikschubert]

LGTM 🚀

I'd be curious to see at some point what subset of jsonpath stepfunctions on AWS supports, but I guess for now just depending on jsonpath_ng and its support should be fine for most use cases. 👍