Nested StateMachine startExecution.sync:2 is not supported in Local StepFunction docker image

This is a (Bug Report)

Description

For bug reports:

• What went wrong?
  • startExecution.sync:2 is not supported in Local StepFunction docker image
• What did you expect should have happened?
  • sync:2 is working and same behavior as the StepFunctions in AWS console
• What was the config you used?

{
  "Comment": "Hello World Main",
  "StartAt": "HelloWorldMain",
  "States": {
    "HelloWorldMain": {
      "Type": "Task",
      "Resource": "arn:aws:states:::states:startExecution.sync:2",
      "HeartbeatSeconds": 60,
      "Parameters": {  
        "StateMachineArn":"arn:aws:states:us-west-2:661617860809:stateMachine:HelloWorld",
        "Input": {  
          "Comment":"Hello world!",
          "AWS_STEP_FUNCTIONS_STARTED_BY_EXECUTION_ID.$": "$$.Execution.Id"
        }
      },
      "End": true
    }
  }
}

• What stacktrace or error message from your provider did you see?

2021-01-16 00:20:41.265: arn:aws:states:us-east-1:123456789012:execution:ApplicationApproval-Dev:460b67cc-a770-4e47-a78d-b04d14cb8712 : {"Type":"ExecutionFailed","PreviousEventId":24,"ExecutionFailedEventDetails":{"Error":"States.Runtime","Cause":"An error occurred while scheduling the state 'ApplicationScreeningWorkflow'. The provided ARN 'arn:aws:states:us-east-1:123456789012:states:startExecution.sync:2' is invalid."}}
Execution ARN: 

For feature proposals:

• What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.
• If there is additional config how would it look

Similar or dependent issues:

• None

Additional Data

• Serverless Framework Core Version you're using:
• The Plugin Version you're using:
• Operating System:
• macOS 10.15
• Stack Trace:
• Provider Error messages:

Start by reproducing the supplied nested state machine configuration against the local StepFunctions Docker image and compare it with the expected AWS behavior. Trace how the plugin handles the arn:aws:states:::states:startExecution.sync:2 resource, then verify that the configuration executes successfully locally without the invalid-ARN error.