Register FastMonitoringService as concrete type to Service system

[Dr15Jones]

Everywhere that request the MicroStateService from edm::Service eventually does a C++ cast to FastMonitoringService*. It would be much better to just register the service as FastMonitoringService instead of as the base class.

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @Dr15Jones.

@smuzaffar, @antoniovilela, @Dr15Jones, @makortel, @sextonkennedy, @rappoccio can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[Dr15Jones]

assign EventFilter/Utilities

[cmsbuild]

New categories assigned: daq

@emeschi,@smorovic you have been requested to review this Pull request/Issue and eventually sign? Thanks

[Dr15Jones]

The MicroStateService class is empty (i.e. no member function or member data). That entire class should just go away.

Or much, much better MicroStateService should gain abstract virtual functions for all the methods modules use from FastMonitoringService and then all module should just talk through those virtual methods. Then FastMonitoringService should move to the plugins directory. This would allow FWCore/ActivityRegistry dependency to be dropped from EventFilters/Utilities which would decrease our overall physical dependencies in or libraries.

[smorovic]

Agreed, MicroStateService is legacy class that should be dropped, so we will prepare these changes.
To drop FWCore/ActivityRegistry dependency, I assume that we also need to move EvFDaqDirector to plugins.