H2 data file gets locked during rollout deployment strategy in authoring templates

Today, when using the rhpam-authoring.yaml template to create a BC + Kieserver environment, the database H2 data file gets locked if the Kieserver pod needs to rollout for some reason (like a env variable update):

        Caused by: java.lang.IllegalStateException: The file is locked: nio:/opt/eap/standalone/data/rhpam.mv.db [1.4.193/7]

    	at com.h2database.h2@1.4.193.redhat-2//org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:766)
    	at com.h2database.h2@1.4.193.redhat-2//org.h2.mvstore.FileStore.open(FileStore.java:173)
    	at com.h2database.h2@1.4.193.redhat-2//org.h2.mvstore.MVStore.<init>(MVStore.java:348)
    	at com.h2database.h2@1.4.193.redhat-2//org.h2.mvstore.MVStore$Builder.open(MVStore.java:2923)
    	at com.h2database.h2@1.4.193.redhat-2//org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:154)
    	... 37 more

This happens because:

1) The JDBC connection URL is opening for local use only, locking the file for a single process use
2) The /opt/eap/standalone/data directory is being used to mount the H2 data file. This directory is not supposed to be used for any reason, since it's used by the Artemis ActiveMQ and is locked by it.

We need to address this bug by implementing the H2 Mixed Mode into the URL for every datasource using this database in the template (rhpam and rhpam_EJB_Timer).