gstlal_ll_inspiral_pipe: scale up number of aggregator jobs to keep up with real-time, gstlal_ll_inspiral_aggregator: add more specific group_id to not conflict with other aggregator jobs

Enabling rpmbuild in the CI pipeline. Modfied burst's spec.in to remove undefined doxygen dependency and strange environment script. Implemented --disable-massmodel in gstlal-inspiral.spec.in to limit the size of the rpm

lloidhandler.py: change structure of data stored and pushed to kafka within EyeCandy, change name of state routes, add logic to handle sampling rates of state info here rather than downstream

gstlal_ll_inspiral_pipe: modify number of aggregation jobs, add option to switch between influx and hdf5 agg backends

- bump min ligo-segments to 1.2.0
- also set gstlal-burst's package metadata to depend on ligo-segments instead of glue-segments

- a few things did not get converted to ligo.segments and lal.LIGOTimeGPS, this patch fixes

update Makefile.online_analysis with online web deployment, add inspiral dashboard yaml configuration

aggregator execs + ll_inspiral_pipe: allow more control with number of routes processed per job, increase number of aggregator jobs in online dag for scalability

gstlal_ll_inspiral_pipe: rename output dir for gstlal_ll_dq for consistency, create multiple gstlal_ll_inspiral_state jobs to handle aggregation better

- 14cf8072 introduced a ln L offset for singles but put it into the numerator.  that is not allowed:  the numerator (and the denominator) must be the *real* distribution density for signal (and noise) candidates, we rely on that being true for astrophysical rate estimation (and false-alarm probability measurement).  ranking statistic hacks go into the ranking statistic, which we define based on these two PDFs in far.py

- make the exclusion of sub-threshold triggers from the kwargs_from_triggers() method permanent, and put an assert into .__call__() to make sure no sub-threshold SNRs leak in.

--event-chisq to plot an snr and chisq on the snr chisq plots

- allow the threshold to be adjusted manually (default is the current
  behaviour, which is to set the threshold from the lower bound of the
  extinction model's domain of validity)

- weren't used for anything, adds baggage to the code.  in the future, it
  might be worth adding an option to select which offset vector to process,
  but none of what this patch removes would be used for that