Configuration and Installer changes necessary to support SSL on JMS

Description of problem:

As of 6.0.2 (because of BZ 1067772), the JMS API requires SSL in order to send some of the messages (those containing the password of the user).

Version-Release number of selected component (if applicable):

Starting with 6.0.2.ER1

How reproducible:

Always

Steps to Reproduce:

This bug is to track the following config and installer changes.

• BPMS installer changes:
  : keystore generation for the server
  : keystore(/truststore) generation for the client
  : configuration change to the standalone*xml files (adding a JMS SSL netty connector)
• Configuration changes (when not using the installer)
  : configuration change to the standalone*xml files (adding a JMS SSL netty connector)

Additional info:

DOCUMENTATION: we will have to add a section to the JMS documentation explaining the following:

1. SSL is needed in order to send certain JMS requests (because they contain the password)
2. How to setup the (BPMS) Remote Java API client to send requests via JMS/SSL.

Lastly: as part of this fix, I've added a new "factory builder" API to the (BPMS) Remote Java API client to make the remote client configuration easier and friendly. I/We also need to document this.