TrigT1CaloMonitoring: Do not renounce inputs for monitoring algorithm.

EfexMonitorAlgorihm was renouncing its inputs. But that means in MT jobs, it may run at any time. In particular, it was observed running at the same time the inputs were being made, leading to crashes. This fixes failures seen in the test_bulkProcessing_data22_900GeV.sh ART test.

It appears that what is happening here is that the algorithm is configured to look for two different inputs, each of which may or may not exist. The algorithm was checking at runtime and ignoring those that don't exist. But this was causing warnings, and the response to the warnings was to renounce the inputs. But as seen above, this is wrong. The correct thing to do is fix the configuration so the algorithm is only looking for inputs which actually exist.