CLOUDP-330230 - start using release-* Evergreen workers for release process

[MaciejKaras]

Summary

This works is towards https://jira.mongodb.org/browse/DEVPROD-17780.

Apart from changing distros for release tasks we need to add our master and release evergreen projects to single task distros allowed list ✅

Proof of Work

CI passing means that the evegreen files are properly validated.

I also triggered some release variants to test the single task distros:

• https://spruce.mongodb.com/version/6870cb22e4a7fa0007ee6ac7/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC
• https://spruce.mongodb.com/version/6870cab02ffaa40007fd0055/tasks?page=0&sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC&variant=%5Epublish_om60_images%24
• https://spruce.mongodb.com/version/6870cf1b1a0d3a0007bfc6bc/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you checked for release_note changes?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Our Short Guide for PRs: Link
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question

[leafnunes]

evergreen retry