MVP for continuous integration and continuous releases

[ScottTodd]

We have the building blocks for CI/CD pipelines but need to connect them all together and get them running automatically. Specific tasks are tracked in subissues, organized in this project: TheRock CI/CD 🪨🚀 (view). By the end of this sprint, we should have:

• Pull requests build for a subset of supported configurations (gfx targets, operating systems, release configurations, etc.)
• Once a day, release builds for all targets we have added so far will be published, using code from the main branch in this repository
• Pull requests test a subset of supported configurations and a subset of all available tests using currently available runners
  • Build Linux Packages fails to Configure AWS Credentials when triggered by a fork #203 will be needed to support PRs from forks
• The main branch in this repository will closely track the mainline or develop branches of ROCm sub-projects in its submodules
• Depending on runner availability, we will run smoketests and longer test suites on release builds.
  • The level of validation we have performed will be reflected somewhere (release pages, repository markdown file, etc.)
• Instructions for how to install nightly releases will be kept up to date at https://github.com/ROCm/TheRock/blob/main/RELEASES.md

Follow-up work for future sprints:

• Expand the build/test matrix, particularly for more GPUs as we bring device labs online
• Add configurability to workflows based on changed files or requested jobs #199
• Optimize CI/CD builders #132
• Support for testing changes to ROCm sub-projects ahead of when they are merged to their own repositories? (including cross-project changes)