feat: full_chain_test.py config with command-line options (#3811)

`full_chain_test.py` supports all options from `ckf_tracks.py` (generic detector), `full_chain_odd.py`, and `full_chain_itk.py`, as well as some new additions to help with testing.

The idea is to complement those scripts which provide *examples*, where `full_chain_test.py` simplifies running interactive/batch tests with different options specified on the command-line. With all the options, it is not intended to be an easy-to-read example. The existing example scripts could eventually be simplified, since they no longer need to support those test options they do have.

The hope is that, in future, `full_chain_test.py` can be used to test new features and see the result in (at least) ODD and ITk environments.

The idea for this initial version is:
* `full_chain_test.py` exactly matches `full_chain_odd.py`
  * ODD configuration is the default
* `full_chain_test.py -A -M1 -N2` exactly matches `full_chain_itk.py`
  * `-A` selects the ATLAS ITk configuration
  * `-M1 -N2` (or `--gen-nvertices 1 --gen-nparticles 2`) changes to 2 particles per event from `full_chain_odd.py`'s default of 800 (`-M 200 -N 4`)
* `full_chain_test.py -G` is similar `ckf_tracks.py`
  * `-G` selects the generic detector configuration
  * does not exactly match the more rudimentary `ckf_tracks.py`, and doesn't try to reproduce seeding config.

Later, if this becomes a useful development test, we can harmonise the detail setup between ODD and ITk.

Also, do we need to support options from `full_chain_itk_Gbts.py` and `full_chain_odd_LRT.py`?