Describe the feature you'd like

A way of tracking the reason for a team working on a project to be away would be very useful.

Pre-existing Issue or Justification

(From @Lordfirespeed) A project could be disabled for many reasons:

• The team has repeatedly not been found by judges so is disabled until the team is located. This could be done automatically.
• The team's area (their guild) has been sent for lunch.
• The team's placement is low. We prefer to allocate judge resources to the top of the rankings as this information is more useful to us when choosing winners.

There are certain scenarios where this information being tracked would be very useful:

• Team is disabled for being not found.
• Team is disabled because their guild has been sent for lunch.
• Team is re-enabled when their guild returns from lunch. In this case, the team should remain disabled even after their guild returns from lunch, but the present behaviour is that they do actually get re-enabled.

Note that this is a similar issue to #23.

Additional context

The action could be a text field reason and an associated time when, such as the following:

{
    "reason": "lunch",
    "when": Date(...),
}

On the client side, there could be a list of pre-defined reasons from a drop down list. An Other option would allow custom reasons.

From the admin portal, when choosing to hide a project, this could produce a popup with these options. One possible implementation would be to modify the /project/hide endpoint (see in docs) to have an additional (maybe optional) reason parameter.