Fix velo lumi counters: ignore out-of-range velo sensor IDs

VELO sensor IDs should be in the range 0-207, however, a small number of events seem to contain clusters with incorrect IDs in the range 208-255. Currently this causes the VELO cluster lumi counters to be set to their maximum value for such events. After discussing with @gbassi, we agreed that a better solution would be to simply ignore clusters from such banks.

This MR removes the code to set counters to max and continues to the next cluster.