MDLSITE-7296 Apply in the queue managers towards using rank

[stronk7]

This changes the picking order of both the normal and the continuous queue managers from previous:

• Integration priority.
• Issue priority.
• Number of votes.
• Last update/comment.

To a new:

• Integration priority.
• Issue rank (calculated elsewhere).

Worth noting that, together with the move we are also disabling a few previous automatisms:

• Moving "important" issues from the candidates to the current queue. Now we are only moving issues by the new agreed sorting method above.
• Stop raising the integration priority to 1 for issues waiting in the queue for more than X (configurable) days.

Also, worth noting that we aren't changing at this stage the 2 jobs in charge of managing the Integration priority of issues:

• set_integration_priority_to_zero.sh
• set_integration_priority_to_one.sh

And they continue applying for the same logic as previously to control such a priority, namely:

• Set the integration priority to 1 if the issue (any of):
  • Has the mdlqa label.
  • Has a Must fix X.Y version.
  • Has the security flag.
  • Comes from CLR
  • Is blocking others (and is not blocked by others).
• Set the integration priority to 0 if the issue (any of):
  • Has null integration priority.
  • Has been reopened.
  • Has integration priority = 1 and is blocked by others.

[junpataleta]

Thanks, Eloy. Looks straightforward and is in line with what has been discussed.