Support the new JSONata expressions

[massfords]

Describe the bug There are new fields introduced to support JSONata data transformations. See this blog post: https://docs.aws.amazon.com/step-functions/latest/dg/transforming-data.html

To Reproduce

Use the state machine referenced from the blog post here: https://github.com/aws-samples/serverless-account-signup-service/blob/jsonata-variables/statemachine/application_service.asl.json

Expected behavior

We should accept this definition instead of reporting errors

Version: 3.9.0

Additional context This was announced as a new feature Nov 22, 2024. The initial fix is likely small changes in the schema files and some validators:

• Pass state needs the Assign field
• Support Arguments and Outputs fields which are mutually exclusive with InputPath, Parameters, ResultSelector, ResultPath and OutputPath fields
• Each state needs to support a QueryLanguage field which is either JSONPath or JSONata
• Top level state also gets QueryLanguage

Additional work that could follow in separate issues:

• provide syntax checking of JSONata expressions
• validate expressions that use functions to ensure they're known and have the correct number of args
• ensure any referenced variables in expressions are resolved within the current scope

[massfords]

I'll have some time later this week to update the schemas. I'll update this issue with details/corrections after I read the spec more closely to understand the impact. I just saw this today and wanted to make some notes on it.