* add `riemannFit` and `gpu` modifiers and workflows for Riemann fit and GPU modules
* switch GPU modules with `gpu` modifier

* add a DQM sequence for pixel-only tracking
* add pixelTrackingOnlyDQM sequences to the pixelTrackingOnly workflows
* add pixelTrackingOnlyDQM sequences to the riemannFit and gpu workflows

  - the CPU Riemann fit works using all combinations between the 2 booleans: `useErrors` and `useMultipleScattering`;
  - the standalone version of the GPU Riemann fit has been updated in order to explore all possibilities among the 2 booleans above: all of them work and produce identical results up to 1e-5 precision (the default one, 1e-6 fails when enabling multiScattering, most likely due to matrix inversions);
  - the GPU version of the Riemann fit within CMSSW works, with 1 fit assigned to each thread, with 32 threads/warps, all dynamically computed.

Things that needs a "hack":

  - limit the "dynamic" size of Eigen matrices to at most, 4x4, which is just fine for quadruplets. Using anything wider will cause errors which I *believe* is related to the stack size of threads on the GPU;
  - cast matrices to be inverted to 4x4 (was done before the previous point: will revert it back and see if that's still needed or not, but I believe it is); this was done in order to "specialize" the `invert()` call to something that is "natively" supported by Eigen on GPU (that brought in also few `__host__` `__device__` here and there in Eigen);
  - fix the alignment of the `struct` holding the results of the fit, since its size was different on GPU and CPU, causing an annoying off-by-one effect.

…07-24-2300

update relval input strings (102X)

…zero-suppression (with normal ZS repacking),RECO of 2015 PbPb VirginRaw data

[10.2.X] add HEM-15-16 relval workflows

backport [10.2.X] add 3 production workflows for premix2018

Merge the Riemann and broken line fits into single configurable pixel
n-tuplet fitter, and extend it to work with up to 5 hits.

Mmake the broken line fit the default algorithm.

Try both triplets and quadruplets in the pixel "hole".

Limit pT used to compute the multple scattering.

Use the inline Cholesky decomposition.

Generic clean up and improvements.

Update the definition of the Patatrack workflows to avoid conflicts in CMSSW_11_0_0_pre12:
  - renumber to avoid conflicts with cms-sw#27392
  - reimplement the definition following cms-sw#28281
  - add Z->mumu 2018 realistic workflows
  - add TTbar and Z->mumu 2021 realistic workflows
  - move the data workflows to 2018D, HLTPhysics and JetHT

…#30338)

…sw#30350)

Backport cms-sw#30105: add ECAL-only workflows for data.
Backport cms-sw#30136: add HCAL-only workflows for MC and data.

Update the RelVal workflows and the CPU customisation:
  - change the .501 workflow to run the full Patatrack pixel track reconstruction on CPU
  - add a customisation to run the Patatrack reconstruction with triplets, on CPU and GPU
  - add the .505 and .506 workflows to reconstruct triplets, on CPU and GPU

Co-authored-by: Andrea Bocci <andrea.bocci@cern.ch>

…odifiers (cms-sw#32333)

The 2018 GPU matrix WFs (10824.502, 10824.512, 10824.522, 10842.502) produced the same cmsDriver configurations as their CPU counterparts. This PR fixes this by setting the gpu modifier also for the RecoFakeHLT step.