Currently each quickstart has its own GitHub CI workflow at https://github.com/wildfly/quickstart/tree/main/.github/workflows , which has the good of full quickstarts independence, yet at same time it seems to be inefficient runtime wise, since most runtime is about Maven downloads, being repeated over and over for each quickstart.

We should figure out a way to improve this runtime, which may mean we switch to the model of the Kubernetes CI workflow, which is a single workflow responsible for creating a test for each quickstart that changed. This model would allow us to first create a full build, which would expose the maven repo for each quickstart...