GEMMonitor should be deleted

Summary

GEMMonitor was intended to allow applications in the gem suite to have general monitoring capabilities in their respective monitor tabs, but as the monitoring has become more consolidated, the need for a centralized monitoring class is not necessary. Furthermore, GEMMonitor, is simply a wrapper for a timer and Infospaces for variables to be held on to. Since the processing of monitorables is being moved to the javascript/html page itself, the infospaces are overkill and the timer can be added to a class on a as-needed basis.

For this reason, the GEMMonitor class is redundant can can probably be removed.

!39 (closed) And previous attempts at MRs have tried to refactor the GEMMonitor class to being just a centralized timer factor, but this is probably not needed, especially as the gemmonitor area has been refactored.

This issue makes even more sense as the general xdaq structure changes in the future (e.g. removing the monitorTab from the xdaq default page basically neuters all of the need for GEMMonitor)

There may be a use to this class, but at the very least, a heavy refactor should be due to this class