[SFN] Enhancements for Map State

[MEPalma]

Motivation

• Adds support for correctly handling ItemSelector and Parameter definitions in Iteration Components, which failed in cases in which the ItemsPath would misuse the environment's stack when the program input was the memory state directly
• Adds support for distributed mode for legacy Iterator declarations (Closes: bug: stepfunction v2 does not handle distributed processing mode correctly #10189, also mentioned in: bug: Step Functions - An error on a map iteration does not fail the State Machine #9970)
• Adds several tests for both inline and distributed mode using ItemSelector and Parameters

Changes

• Added distributed legacy iterator components
• Added related grammar support for processor config in legacy iterator
• Adjusted the behaviour of ItemsPath
• Several related changes regarding the misuse of the program's stack
• Several adjustments to map run logic
• Added related tests

[coveralls]

coverage: 83.411%. remained the same
when pulling 274c2b8 on MEP-sfn-dist_legacy_iter_and_others
into 6ec63bf on master.

[github-actions]

LocalStack Community integration with Pro

    2 files  ± 0      2 suites  ±0   1h 26m 13s ⏱️ - 2m 28s
2 681 tests +10  2 428 ✅ +10  253 💤 ±0  0 ❌ ±0 
2 683 runs  +10  2 428 ✅ +10  255 💤 ±0  0 ❌ ±0 

Results for commit 274c2b8. ± Comparison against base commit 6ec63bf.

♻️ This comment has been updated with latest results.

[dominikschubert]

LGTM, great changes and awesome test coverage!

[dominikschubert]

what would be the strategy to test this? Can this be achieved with certain state machine configuration or would we need to somehow inject errors?

[MEPalma]

Adding some state machines that raise error in the MapRun would inform us about this exact behaviour, but this is very connected to the tolerance control aspects of MapRun which will need supporting from both the provider side and the MapRun backend.