feat: Allow specifying compute environments for queue

[usulkies]

Description

Allow specifying compute environments for a job queue, and fix an issue when there are more than 3 compute environments.

Motivation and Context

Job queue should have maximum 3 compute environments associated with it. Current version attaches ALL compute environments to all job queues, which is an issue because if more than 3 compute environments are defined - the apply will fail. In addition, the module do not allow specifying compute environment(s) to be used by a specific queue.

Breaking Changes

No

How Has This Been Tested?

• [x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
• [x] I have tested and validated these changes using one or more of the provided examples/* projects
• [x] I have executed pre-commit run -a on my pull request

[github-actions[bot]]

This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days

[usulkies]

Who's responsible for reviews?

[antonbabenko]

This issue has been resolved in version 2.0.0 :tada:

[github-actions[bot]]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.