Enable Trafodion Installer use in test process

Scripts now check to see if cloudera manager or ambari are installed.
If so, then use trafodion installer to install/uninstall trafodion
instance.
Otherwise, use the current start/stop instance scripts that run instance
in the build tree.

For installation in non-build location and running sql regressions,
the sql dev regression tarball is also installed.

Put common location variables like WORKSPACE in traf-functions.sh.

Re-work source_env function so it figures out where to find correct
sqenv file and does not require caller to be in correct directory.

Add missing owner/group/mode attributes in cdh.pp (found in testing
when puppet master files were not owned by root).

I tested that the re-worked buildtest scripts work okay on a current cdh44 node
(passed node_test job).

The trafodion installer path won't work until we add JJB steps to existing
jobs to build dcs and installer in every job that wants to run an instance.
This changeset only changes node_test job to enable testing. All other job
changes will be in a separate change-set.

There will also need to be a separate change set to save logs from the install
location instead of the build location, once we identify the correct paths.

blueprint: infra-test-installation

Change-Id: If94e4c5235ee7908e33aa2ea66532238dae23bbd