Remove mandated MR milestone
It seems that people without the developer rank can't assign a milestone to a MR, which means all new MR pipelines will fail until someone with access assigns a milestone.
This probably requires to rethink a bit the automated benchmarking, but maybe it would only be a manual/nightly job given that the current machine load makes the results inconclusive