Bundled settings are broken #3490
Description
Before #3250, I could bundle a settings.ini in the site-specific product, and still launch with several -settings on the command line option.
So the SNSProduct/settings.ini file would contain settings that are global to our site, settings that work for office use.
On beam lines, our launcher adds -settings /path/to/beamline/settings.ini, and in some cases additional specializations via another -settings /path/to/special.ini.
After #3250, having any -settings arguments causes the launcher to ignore bundled settings?!