The public CI/CD and release pipeline is needing attention

[karlmutch]

As an open source user and maintainer
I want to be able to reliably use either free or self hosted resources for CI/CD without relying on an external actor
In order that public enhancements, testing, and releasing and be performed

A private CI/CD pipeline has been operating for sometime outside of the public release strategy. We wish to resurrect the ability for releases on StudioML to become more automated from a public perspective using publicly available platforms.

Originally the CI/CD was being done using a tangle of Sentient funded accounts and facilities. This lead to eventual devops rot so that automated and pipeline testing dont really exist outside of Sentients own infrastructure. We would like to change this and put some effort into creating a long term sustainable means by which both ourselves and others can return to formally releasing new StudioML versions openly.

[xujiamin9]

Implement release engineer input for which tests to run, currently hardcoded as is_on_aws() and is_on_gcp() in studio/util