Based upon the data collected from the 'gridperf' binary, keep a table of events type type 'mbdreconfig' & 'mbdrestart' and present in RTM

This is important as we don't often time capture a restart or a reconfig, it could even be as a result of a binary that is segfaulting and being restarted by LIM. It would be nice to be able to track these similar to the table below: MariaDB [cacti]> select * from grid_clusters_events order by event_time desc limit 40; +-----------+-------------+---------------------+---------------------+ | clusterid | type | event_time | event_seen | +-----------+-------------+---------------------+---------------------+ | 50 | mbdreconfig | 2022-01-30 06:03:33 | 2022-01-30 06:09:12 | | 9 | mbdreconfig | 2022-01-30 05:01:52 | 2022-01-30 05:08:34 | | 127 | mbdreconfig | 2022-01-30 04:00:25 | 2022-01-30 04:09:03 | | 50 | mbdreconfig | 2022-01-29 23:06:59 | 2022-01-29 23:19:04 | | 50 | mbdreconfig | 2022-01-29 21:34:52 | 2022-01-29 21:38:32 | | 50 | mbdreconfig | 2022-01-29 21:04:00 | 2022-01-29 21:09:02 | | 47 | mbdstart | 2022-01-29 21:03:27 | 2022-01-29 21:09:02 | | 50 | mbdreconfig | 2022-01-29 20:53:58 | 2022-01-29 20:59:10 | | 38 | mbdreconfig | 2022-01-29 20:38:28 | 2022-01-29 20:48:51 | | 50 | mbdreconfig | 2022-01-29 20:23:20 | 2022-01-29 20:28:59 | | 50 | mbdreconfig | 2022-01-29 20:02:49 | 2022-01-29 20:09:07 | | 53 | mbdreconfig | 2022-01-29 19:38:49 | 2022-01-29 19:49:30 | Based purely on the results of gridperf capturing those date changes.