[WFLY-2994] Improve messaging connector param resources

* check when a transport parameter resource is added if the parameter
  name is allowed by the parent transport configuration. If it is not
  accepted, HornetQ will log a warning, the server will be started
  but the transport itself will not be started.
  This check ensures that a misconfiguration will result in a failure at
  the MODEL stage instead of waiting for a client to use the transport at
  runtime and it is not available.
* update messaging XML configuration files used in the test that were
  not correct in that regard.

JIRA: https://issues.jboss.org/browse/WFLY-2994
Fix Vault logging messages

Uses different i18n key for password prompt and password confirmation
prompt.

Current english output is incorrect as the WFLYSEC is prepended to the
again message:

WFLYSEC0052: Enter Keystore passwordWFLYSEC0061:  again:

More generally, language do not necessarily put their "again" equivalent
at the end of the sentence. E.g. in French, that would be "Saisir à
nouveau votre mot de passe" where "a nouveau" (aka again) is in the
middle of the sentence
use NONE id for vault tool's messages

to prevent display WFLYSECXXX before each message
Remove 7.1.2 test controller

- for now we just skip all tests that ware testing 7.1.x compatibility
Remove 7.1.x legacy models
WFLY-3380 Add JACC support to SimpleSecurityManager.isCallerInRole
Merge pull request #6310 from jmesnil/WFLY-2994_messaging_transport_param_resources

[WFLY-2994] Improve messaging connector param resources
Merge pull request #6339 from jmesnil/fix_vault_logging_message

Fix Vault logging messages
Merge pull request #6349 from ctomc/test-framework

Remove 7.1.x test controller
Merge pull request #6358 from sguilhen/master

WFLY-3380 Add JACC support to SimpleSecurityManager.isCallerInRole