Introduce pipeline configuration files

[lasch]

Allows to specify a profile or personality for the processing pipeline (-P <filename>) parameter.

The profile is a json file listing the stages/callback functions in their correct order and specifying whether they should be enabled (true) or not (false). Any name not appearing is as if it was set to false.

This allows to create pre-sets for recurring workflows without requiring to provide a long list of cmd line args.

The default assumes all stages potentially enabled (depending on command line options).

[mcalman]

Should we silence warning/info logs that don't apply to the selected stages?

For example, with the following profile:

{
    "stages": [
        {"remove_ids_from_name": true}
    ]
}

I get the following logs that aren't relevant with my selected stages:

2025-07-15T10:11:41.507758  WARNING rcu_util counter requested but no compiler log provided. No utilization will be plotted. 
2025-07-15T10:11:43.071832     INFO Partial-overlap slices resolved: 0 
2025-07-15T10:11:43.071880     INFO PEC event stats o/i: 0 / 0 
2025-07-15T10:11:43.071891     INFO PEC event stats o/i: 0 / 0 

Otherwise, all functionality looks good to me!

[lasch]

Removing output from deactivated stages is a great suggestion. Lets open an issue to keep this on the radar.