Do not cache CMR configuration properties

The CMR configuration properties in the JTAEnviornmentBean such as commitMarkableResourceJNDINames, for example, are stashed in various places (eg [1] and [2]).

This can present problems when used in an application server by a deployment: when the application is undeployed the jndi name is left in the JNDINames collection. See the linked WFLY issues for why this could be an issue.

This Jira refers to all CMR properties but an analysis should be made as to which ones must be dynamic and which ones can be fixed. 

[1] https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/CommitMarkableResourceRecordRecoveryModule.java#L123

[2] https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/TransactionImple.java#L1748