As a consequence a loaded module cannot be loaded a second time in force
mode. So the check of this situation in conflict procedure is not useful
anymore as the TESTSUITE_ENABLE_SITECONFIG_DEBUG non-regression test.
Separator ';' is used instead of ':' on Windows platform. Add a test
leveraging siteconfig.tcl-1 to check path variable handling on a fake
Windows platform.
Set/get default path variable separator with new getPathSeparator
procedure. This way, global variable g_def_separator is defined after
parsing the siteconfig.tcl.
Adapt defined modulepaths in example testsuite configuration file
(modulerc and .modulespath) depending if versioning installation mode is
enabled or not.
Add 'install-testsiteconfig' make target to setup a dummy siteconfig.tcl
file in install_etcdir. Link that to some of the travis checks to run
testsuite with an existing siteconfig.tcl