Switch to auto-scheduled setup for azure and azure_eastus2 ci runs

[LoopedBard3]

Switch to auto-scheduled setup for azure and azure_eastus2 ci runs. This includes adding the .json configuration files for specifying the jobs to schedule, updating the yaml schedules themselves, and adding individual machine profiles for the azure machines. I have one more set of machines and jobs to add and then will finalize and add the scheduler I have been using to the repo.

Can't test run the pipelines as the profiles are needed but will make sure to watch the pipelines for success.

[DrewScoggins]

I assume this is work to move the Azure schedules over to what we were already doing for the other benchmark CI runs, right? If that is the case, do we have some list of what the previous schedule was to make sure that we are not missing any runs by moving how we generate them?

[LoopedBard3]

The goal of this is to update the Azure Schedules with the new json schedule format for use with the soon to be in PR scheduling tool rather than the manual scheduling. I did a comparison between main and the PR and they both have the same tests running for the azure and azure-eastus2 schedules, although in different orders and with different names. The set of tests running for each are as follows (new names):
Azure:

Containers_Azure_Server_Arm64 Containers_Azure2_Server_Amd64 Baselines_Database_Azure_Server_Arm64 Baselines_Database_Azure2_Server_Amd64 Baselines_Azure_Server_Arm64 Baselines_Azure2_Server_Amd64 Trends_Azure_Server_Arm64 Trends_Azure2_Server_Amd64 Trends_Idna_Amd_Lin Trends_Idna_Amd_Win Trends_Idna_Intel_Lin Trends_Idna_Intel_Win Trends_Database_Azure_Server_Arm64 Trends_Database_Azure2_Server_Amd64 

Azure-eastus2

Containers_Cobalt_Cloud_Lin_Server Containers_Cobalt_Cloud_Lin_Server_Azure_Linux3 Baselines_Database_Cobalt_Cloud_Lin_Server Baselines_Database_Cobalt_Cloud_Lin_Server_Azure_Linux3 Baselines_Cobalt_Cloud_Lin_Server Baselines_Cobalt_Cloud_Lin_Server_Azure_Linux3 MVC_Cobalt_Cloud_Lin_Server MVC_Cobalt_Cloud_Lin_Server_Azure_Linux3 Trends_Cobalt_Cloud_Lin_Server Trends_Cobalt_Cloud_Lin_Server_Azure_Linux3 Trends_Database_Cobalt_Cloud_Lin_Server Trends_Database_Cobalt_Cloud_Lin_Server_Azure_Linux3 

Both sets are running the same tests, but the normal azure set also has the IDNA machines running tests. As noted, I did a comparison of the tests that are set to run before and after and no tests are missing.

[LoopedBard3]

Force-pushed to include the clean-up of non-required configuration options in the azure.yml file. (preferred_partners and default_profile are not required).

[DrewScoggins]

LGTM