Feature/array node workflow parallelism

[pvditt]

Tracking issue

flyteorg/flyte#3924

Why are the changes needed?

Want to add support for array node map tasks to utilize threads under the parent workflow's set parallelism. Decrease confusion on default/expected map task parallelism

What changes were proposed in this pull request?

Set default parallelism to None. If a user bumps their Flyte version to include flyteorg/flyte#5214 this will default the array node map task to utilize the parent wf's parallelism. If a user has an older flyte version this will map to 0, which will maintain the existing parallelism behavior.

NOTE this will cause cache misses on the first re-runs as the hashed name will change

How was this patch tested?

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

flyteorg/flyte#5062 + flyteorg/flyte#5214 were already merged

Docs link

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.57%. Comparing base (f4d894a) to head (451fd03).
Report is 22 commits behind head on master.

❗ Current head 451fd03 differs from pull request most recent head 3f596c2. Consider uploading reports for the commit 3f596c2 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #2268       +/-   ##
===========================================
- Coverage   83.09%   53.57%   -29.52%     
===========================================
  Files         324      180      -144     
  Lines       24860    18133     -6727     
  Branches     3761     3547      -214     
===========================================
- Hits        20657     9715    -10942     
- Misses       3582     7991     +4409     
+ Partials      621      427      -194     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[eapolinario]

Can you fix the unit test failure? The error:

FAILED tests/flytekit/unit/core/test_array_node_map_task.py::test_inputs_outputs_length - AssertionError: assert equals failed
  'tests.flytekit.unit.core.test_  'tests.flytekit.unit.core.test_ 
  array_node_map_task.map_many_in  array_node_map_task.map_many_in 
  puts_-6�b^3b�d0^353d�a5d^e6e�8-4d7�9-82921�  puts_b^f51001578�d0^ae197�a5+2c0af0a� 
  -ead2b3�-arraynode'                +99�d^d�89-arraynode'

[pvditt]

Can you fix the unit test failure? The error:

FAILED tests/flytekit/unit/core/test_array_node_map_task.py::test_inputs_outputs_length - AssertionError: assert equals failed
  'tests.flytekit.unit.core.test_  'tests.flytekit.unit.core.test_ 
  array_node_map_task.map_many_in  array_node_map_task.map_many_in 
  puts_-6�b^3b�d0^353d�a5d^e6e�8-4d7�9-82921�  puts_b^f51001578�d0^ae197�a5+2c0af0a� 
  -ead2b3�-arraynode'                +99�d^d�89-arraynode'

@eapolinario oof on my end. Just updated - will re-request your review after the builds pass