General refactoring of names for modules and configuration parameters

Some names in the trigger/triggeralgs repositories are now old / inaccurate. A good example of this is the Horizontal Muon Activity Maker, which is configurable to not only trigger on muons but can also look for adjacencies/multiplicities etc. Additional refactoring should be considered for the schema options for particular plugin/module to make it obvious what module/plugin the option in question belongs to. Example of this is trigger_window_before_ticks which only changes the timing TCs - which is not obvious from the name. Another one would be trigger_rate_hz.

Start by reviewing triggeralgs/src/TriggerActivityMakerHorizontalMuon.cpp and the linked entries in daqconf/config/daqconf_full_config.json. Trace how the module names and schema options are used across the trigger and triggeralgs repositories before defining the affected scope. Done requires an agreed, consistent naming scheme applied to the relevant modules and configuration parameters.