fix(stepfunctions): maxConcurrency does not support JsonPath

[abdelnn]

Issue # (if applicable)

Relates to #20835

Reason for this change

MaxConcurrency does not support JsonPath. This change adds MaxConcurrencyPath so that CDK users can specify a JsonPath for their MaxConcurrency

Note : This does not invalidate JsonPaths for MaxConcurrency, as I'm unsure how to do so without reverting #20279 . Open to suggestions

Description of changes

Added a new maxConcurrencyPath field that accepts a JsonPath value. Decided to go with another explicit field as it is similar to what is done for ErrorPath and CausePath, in addition to most other Path fields

Description of how you validated changes

Added unit tests

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[wong-a]

Some minor comments. LGTM overall

[aaythapa]

Thank you for the PR, changes look good!

This does not invalidate JsonPaths for maxConcurrency, as I'm unsure how to do so without reverting #20279 . Open to suggestions

I'd suggest the same thing Kaizen suggested here and throw a descriptive error when we detect a JSON path in maxConcurrency. Should be backwards compatible as the deployment fails.

EDIT: will deal with JSON path in maxConcurrency separately. Merging this PR for now so that people with the same issue as #20835 have a workaround

Pull request has been modified.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: bcb24b1
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).