[Core feature] Migrate ArrayJob to use TaskTemplate Config and deprecate ArrayJob proto

[EngHabu]

Motivation: Why do you think this is important?

ArrayJob proto has 4 different primitive values that can be filled in. We can cleanup the dependency on a proto and move these params to configs on the TaskTemplate.

Goal: What should the final outcome look like, ideally?

Deprecate ArrayJob proto and leverage TaskTemplate.Config map instead.

This frees up the Custom field to the individual tasks' which opens up the possibility of defining Array Jobs on custom task types.

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏