Send Aliases for update_central_configurations_version_range_v2 job

[mhlidd]

What Does This Do

Given the original state of the script prior to the modifications to the Updated Supported Range job made here, the job would pass under the following conditions:

1. SEND_ALIASES=false, Language implementations in the registry has no aliases
2. SEND_ALIASES=true, Language implementations in the registry has aliases

dd-trace-java had some aliases in the registry and SEND_ALIASES=false, causing the script to fail. The registry has since been migrated to have language implementation aliases, so SEND_ALIASES needs to be set to true to keep the script working for the future.

Motivation

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors

Jira ticket: [PROJ-IDENT]

Note: Once your PR is ready to merge, add it to the merge queue by commenting /merge. /merge -c cancels the queue request. /merge -f --reason "reason" skips all merge queue checks; please use this judiciously, as some checks do not run at the PR-level. For more information, see this doc.

[github-actions]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.