Always load default profile parameters BEFORE profile-specific parameters

When deploying configurations for a profile (e.g.: `settings.myprofile.sh` the developer scripts ignore the default parameter files and expect profile specific (e.g.: `*.myprofile.param`) files to be available.
It would be nice to have the scripts always load default profile parameters - if available - before the profile-specific ones: this would allow an additional level of configuration, and would facilitate deploying components that are shared and have the same configuration across profiles.

Desired behaviour:
- look up parameter files for `default` profile and load them, if available
- look up profile-specific parameter files and load them, if available, overriding/replacing the values previously set by the `default` profile