Setup scripts could provide test TLS certificate

[slominskir]

Currently we rely on Wildfly to generate a test TLS cert on the fly. This works, but each time you navigate your web browser to the app's https URL at the beginning of a browsing session you're prompted to click through warnings about an untrusted cert. A better approach may be to generate a test cert outside of the Wildfly container in the bash setup script and feed it into the Wildfly container via env or bind mount. If created outside of Wildfly, it would be easier to add to a browsers trusted cert store and could be persisted on the user's filesystem for re-use.