Fix FORK_JOIN_DYNAMIC input wrapping when fed directly by JSON_JQ_TRANSFORM (#575)

———

Pull Request type

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Build related changes
• WHOSUSING.md
• Other (please describe):

Changes in this PR

• Normalized JSON_JQ_TRANSFORM outputs so both result and resultList are plain Java maps/lists. In reproduction workflow fork_join_dynamic now receives inputs like

{
	"commonProperty": "common value",
	"property": "value1",
	"__index": 0
}

instead of

{
	"input": {
		"commonProperty": "common value",
		"property": "value1"
	},
	"__index": 0
}

in the version before changes

Also this behaviour matching with Orkes Cloud behaviour.

• tests:
  - JsonJqTransformTest checks resultList equals a list of standard maps.
  - ForkJoinDynamicTaskMapperTest asserts dynamic fork inputs remain unwrapped and keep their parameters.
  - Verified manually on the workflow from issue FORK_JOIN_DYNAMIC adds unexpected input nesting when using JSON_JQ_TRANSFORM output #575. Before fixing the bug, it was reproduced only when JSON_JQ_TRANSFORM went immediately before FORK_JOIN_DYNAMIC; inserting an asynchronous task (WAIT/SIMPLE/...) between them serialized the data and hid the error.

the screenshot from the version before fix with WAIT task

The fix removes this dependency and the need for such workarounds