aws-stepfunctions-tasks: Allow setting task name

[iRoachie]

Describe the feature

When defining step function tasks, the api accepts scope and id as inputs, and the id is used as the name of the task.

e.g:

 const reportFailedTask = new Tasks.LambdaInvoke(
    scope,
    'Publish Fail Status',
    {
      lambdaFunction: reportFailedFunction,
    }
  )

results to a definition like:

 "Publish Fail Status": {
      "Type": "Task",
      "Resource": "arn:aws:states:::lambda:invoke",
      "Parameters": {
        "FunctionName": "arn:aws:xxx",
        "Payload.$": "$"
      }
    }

You can imagine a stack having multiple state machines with a task named Publish Fail Status but since cdk uses the id arg for the construct, it can't be reused.

We should clearly be able to set construct id, separate from the name of the task.

e.g

 const reportFailedTask = new Tasks.LambdaInvoke(
    scope,
    'entity-report-failed-task',
    {
      taskName: 'Publish Fail Status',
      lambdaFunction: reportFailedFunction,
    }
  )

Use Case

I need this feature, cause it's annoying to have to come up with a unique task name per state machine, and it hurts the readability of the definition in the UI.

Proposed Solution

Allow a taskName prop in the task properties.

If supplied use it as the task name, If not, cdk should use the id to ensure this feature is backwards compatible

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.93.0

Environment details (OS name and version, etc.)

Mac OS 13.5.1

[peterwoodworth]

Sounds to me like it might need a feature flag, but I see the pain point. Thanks for the request!