[step-functions] Syth of addCatch on LambdaInvoke

[allankp]

Cloudformation schema validation failure due to the ordering of addCatch on Lambda function invokes within a StepFunction

Reproduction Steps

  const lambdaInvoke = new LambdaInvoke(
    scope,
    'lambdaName',
    {
      lambdaFunction: props.lambdaFunctions.xxxx,
      qualifier: xxx,
    },
  );
  lambdaInvoke.addCatch(xxxx, {
    resultPath: '$.error',
  });
  lambdaInvoke.addCatch(
    xxx, {
      resultPath: '$.error',
      errors: ['Exception'],
    },
  );

What did you expect to happen?

addCatch is created in the CFN from least specific to most specific

What actually happened?

12:59:28 PM | CREATE_FAILED        | AWS::StepFunctions::StateMachine | xxxxx
Invalid State Machine Definition: 'SCHEMA_VALIDATION_FAILED: States.ALL must appear alone and at end of list at /States/lambdaInvoke/Retry[0]/ErrorEquals[0], SCHEMA_VALIDATION_FAILED: States.ALL must appear alone and at end of l
ist at /States/lambdaInvoke/Catch[0]/ErrorEquals[0], SCHEMA_VALIDATION_FAILED: States.ALL must appear alone and at end of list at /States/lambdaInvoke/Retry[0]/ErrorEquals[0], SCHEMA_VALIDATION_FAILED:
States.ALL must appear alone and at end of list at /States/lambdaInvoke/Catch[0]/ErrorEquals[0]' (Service: AWSStepFunctions; Status Code: 400; Error Code: InvalidDefinition; Request ID: d4dfb385-a7b7-4fce-8b2f-bf08773a3abc; Pro
xy: null)

Environment

• CLI Version : 1.57.0
• Framework Version: 1.57.0
• Node.js Version: v10.22.0
• OS :
• Language (Version): TypeScript (3.8.3)

Other

---

This is 🐛 Bug Report