Fix ID Trigger monitoring

After the changesntop the data file and menu many of the trigger chains had changed, and much of the monitoring was not working. After extensive changes, it still was not working since getting the changes to the chains and the analyses was difficult to synchronise.

Therefore some additional scripts to autogenerate the chains dependent config files and so on from a single central config file have been added. These scripts are not ideal - it would be better to use a central config file directly in the jobs, but we have files in python, json files, and files in a custom format, so getting them all to use some central config file would be none trivial.

As many of the jobs and chains are now different, then most of the references will have to be updated so the oportunity was also taken, to fix the default PT cut back to 1 GeV for the moniotring rather than 2 GeV threshold that was being used by default for some reason.

Please note that NONE of the code in TrigInDetValidation, or TrigInDetAnalysisUser is run as part of ANY of the art tests, and the new files in the TrigInDetValidation/utils directory are template conmfiguration files, that get modified automatically to create the actual files, and as such their contents should not be reviewed.