Worker status for competition organizers (from rabbit)

[IdirLISN]

/!\ New PR with modified feature. /!\

The feature is now aware of workers health directly from django to rabbit instead of going through the site worker which slows the app massively. Using rabbit enable the feature to be much more responsive and display the worker state faster. the implementation is easier also.

check the feature at: https://dev.codabench.org/
------------------------------- OLD PR (edited) --------------------------------------

@ mention of reviewers

@ObadaS
@Didayolo
@ihsaan-ullah

A brief description of the purpose of the changes contained in this PR.

This feature enables admin users, competition organisers and his/her collaborators to monitor compute worker activity.
Public compute workers displayed by default and if the competition own a private queue, it displays the private compute workers linked to the queue of the competition.

UI inside of the header of the competition page.

Feature contains:
Feature available only for competition organizers and collaborators.
When disabled or hided behind the button, the websocket connection is disabled for performance.

Issues this PR resolves

Enables organizers to monitor compute workers activity to push them to use their own workers in case of high activity on codabench public compute workers.

A checklist for hand testing

• Try the panel as a organizer, you should be able to see it by pressing the button.
• Submit and watch if the panel shows the activity of the compute worker
• Verify websocket state when the panel is not displayed, the connection should be deactivated.
  (docker compose logs -f django should display websocket open and close with the panel)

Checklist

• Code review by me
• Hand tested by me
• I'm proud of my work
• Code review by reviewer
• Hand tested by reviewer
• CircleCi tests are passing
• Ready to merge

[Didayolo]

Very nice. We need to find a way to stress test this feature on a preprod environment.