Specifying a run-time user account for JOC Cockpit should not require root permissions for the installer

Current Situation

• The JOC Cockpit installer considers a runningUser element in the joc_install.xml response file if the setup is performed using root permissions, i.e. when not using: ./setup.sh -u
• The installer owns certain files and directories to the runningUser and therefore requires to be executed from the root account.

Desired Behavior

• The JOC Cockpit installer should make use of group permissions to allow a runningUser account to start JOC Cockpit:
  • Any files and directories created by the installer using the -u switch are owned by the current user.
    • A number of files and directories are assigned read/write permissions for the owner's group.
    • This allows any later run-time account with the same group membership to run JOC Cockpit.
    • This does not require sudo permission for the currrent user.
  • When omitting the -u switch then the installer has to switch to the root account
    • the files and sub-directories in the <home> directory are owned by the root account.
    • the files and sub-directories in the <data> directory (JETTY_BASE) are owned by the current account.
    • Group permissions for files and directories are similarly considered as for running the installer using the -u switch