fix: use correct cliOptions key for scenarioName in Fargate workers

[barth12]

Summary

The --scenario-name flag was not being passed correctly to Fargate workers, causing them to receive null instead of the actual scenario name.

Root Cause

In generateTaskOverrides(), the condition checked cliOptions['scenarioName'] (camelCase) but the value was read from cliOptions['scenario-name'] (kebab-case):

// Before (bug):
context.cliOptions['scenarioName']
  ? ['--scenario-name', context.cliOptions['scenario-name']]  // reads undefined → "null"
  : [],

Fix

Use the correct camelCase key consistently:

// After (fix):
context.cliOptions['scenarioName']
  ? ['--scenario-name', context.cliOptions['scenarioName']]
  : [],

Related

Fixes #3589 - this appears to be a regression or incomplete fix from #3651

[CLAassistant]

All committers have signed the CLA.

[hassy]

thanks @barth12!