Create Bi-weekly job to run against Quarkus Latest Release

[riprasad]

The existing job has two major drawbacks:-

1. Runs against Quarkus Master - we are likely not going to be able to fix whatever issue that comes out because there is no quarkus release we can use. the issue we have now is like this:-

Error:  /home/runner/work/apicurio-registry/apicurio-registry/app/src/main/java/io/apicurio/registry/rest/v1/ArtifactsResourceImpl.java:[105,185] cannot find symbol
Error:    symbol:   method reusable()
Error:    location: @interface org.eclipse.microprofile.metrics.annotation.ConcurrentGauge

they probably changed some classes or dependency about monitoring, but we cannot fix issues like this in apicurio-registry master because it's 999-SNAPSHOT quarkus.

2. Nightly Build - the builds are done every night and the bandwidth is not sufficient for doing the fix.

Thus, It is better to run Apicurio Registry twice a week and against the latest released version of quarkus. Thereby providing sufficient time for QE to work on the fix.