Improvement suggestions to make checker bundles actually usable

[ClemensLinnhoff]

Is your feature request related to a problem? Please describe.
In my opinion, the current implementation of checker bundles is hardly usable. I am using the ASAM OpenX standards on a daily basis. I like the concept of the checker bundles very much and would be using them also on a daily basis. But dealing with config files for every run, is so much of a hassle, that I am not using checker bundles at all.
I neither want to change a configuration file every time I want to run a check nor do I want to set up a docker pipeline to create config files on the fly.

Describe the solution you'd like

• Make it mandatory for every checker bundle to have a default config.
• Make the default config the actual default. The openscenario xml checker bundle has a -d option, that does nothing. I propose to just use a default config, if no config path is given. No need for a -d option when running the bundle.
• Most important issue: Move the InputFile out of the config and make it a mandatory positional argument of the checker bundles.

With these improvements, running a standard check with a checker bundle would be as simple as

qc_openscenario /path/to/my/scenario.xosc

In a lot of cases I think people will just run one individual checker bundle without integrating it into the framework, running multiple checker and report bundles. And this would simplify it a lot.

Describe alternatives you've considered
Well, the alternative is, keep everything as is and not a lot of people will be using the QC Framework.

[AsamDiegoSanchez]

QC Framework CCB: Agrees with the suggestions and is working on it

[pmai]

Except for the non-mandatory -d option (and other specific argument names), the qc-osi-trace checker bundle more or less matches this approach, by having a useful default configuration, and also allowing override of parameters on the command-line, so that e.g. the input file name can easily be provided on the command line:

qc_ositrace -d -i /path/to/my/scenario.xosc

We could drop the need for -d as well, and even default to positional arguments for the input file - however the latter makes most sense if we can handle multiple input files, which requires further refactoring of the config mechanism.

That being said, all of this only makes sense if we do this in a common way across the bundles...