lazy loading of the parameter set database
The current art eagerly loads the parameter set database from its
input file. "Analysis jobs", i.e. jobs that do not produce any
framework outputs, do not need to load the database unless it is
explicitly queried by the user. With the current software this is
achievable by setting source.readParameterSets to false in the job
configuration. A more user friendly approach to avoid the sometimes
significant overhead (e.g. #10491) would be to only load the parameter
set database when needed, instead of always pre-loading it by default.
The "when needed" cases are writing out a framework format output
file, which should preserve historical parameter set information by
default, or an explicit user query.