The quarkus_flags scenario added in #445 is the only role-based
scenario without the roles -> ../../roles symlink, so in CI its
converge stops with "the role 'keycloak_quarkus' was not found".
Once the role is found, verify fails next: it reads
/opt/keycloak/keycloak-26.7.3/conf/keycloak.conf, but the scenario
installs the role's default version, which is no longer 26.7.3.
Add the roles symlink the other scenarios use and read keycloak.conf
through the /opt/keycloak/keycloak-*/ glob already used in
molecule/quarkus/verify.yml, so the check does not depend on the
installed version. The assertions are unchanged.