Separate weekly openApi-doc refresh and command-metadata refresh

[ramsessanchez]

Split Weekly generation pipeline into two separate pipelines, one to retrieve openApi updates and individually build the modules, and a second pipeline to generate the comandMetadata which requires all modules build on a single image.

The following yml files handle the following:
1.) downloading the most recent openApi docs
2.) determine which modules have been updated
3.) build the updated modules independently to validate openApi document correctness
4.) if all updated modules build successfully then a PR is created with the updated openApi documents.
Weekly-Generation.yml
Individual-Workload-Module.yml

The second will be triggered on merges to Dev and can also be triggered manually.
1.) All modules are built on a single image
2.) the commandMetadata is generated after all modules are built.
3.) successful completion of both results in a pull request into the Dev branch with an updated commandMetadata file.
command-metadata-refresh.yml

Note: The second pipeline is still in testing as we can't test the pipeline fully until we have it registered as one of our pipelines in devops and add the appropriate token.

[MIchaelMainer]

I'm curious how much this reduces the average generation run.

[ramsessanchez]

I'm curious how much this reduces the average generation run.

This won't necessarily reduce generation time. Instead, this will ensure that we are able to catch instances of failure in the modules individually. At the moment, during cases where multiple modules fail, we are only alerted of the first failure. Because all others are hidden, we can only know about one failure at a time bottlenecking us to tackling one failure at a time. This was we can know all the failures at once and tackle them in parallel.