Add administrative brew locking function

[G-Ambatte]

This PR is work towards #3326.

This PR adds a check to the getBrew function that throws an error if the brew stub has a lock object with a state property set to 1 or 2.
State 1: locked, inaccessible.
State 2: locked, only accessible via Edit page.

The intended purpose of this function is to allow administrators to prevent access to brews that have identified issues - for example, DMCA take down requests.

[calculuschild]

This seems fine, and I would be ok merging this to form a basis for the next steps, since it shouldn't break anything. Do you want me to merge it now or keep tinkering on it?

[G-Ambatte]

This seems fine, and I would be ok merging this to form a basis for the next steps, since it shouldn't break anything. Do you want me to merge it now or keep tinkering on it?

I'll keep tinkering for now, I've used lock.state as an integer because I anticipated having multiple states (such as completely locked, or locked for editing only). If it will stay as simple as it is, then it may be more legible to future developers if I were to use named boolean states - such as locked and editable.

[5e-Cleric]

Not sure if this is useful, but there is a 423 - Locked error code.

[G-Ambatte]

MongoDB entry:

Share Page:

Edit Page:

[G-Ambatte]

Includes a locked brew test:

[Gazook89]

I haven’t taken a strong look at this beyond just get comments/screenshots here, so pardon if I missed it:

i think this needs two things: a list of possible reasons the brew is locked (just a static thing, not anything actually related to a specific brew), and a path to contacting “administrators” like a link to the Reddit mod mail or whatever.

Right now it just looks overly harsh, with no indication of what the issue could be and no further help to get it fixed. Part of this is styling (big red letters) and part of it is content.

Further, it might just be best to say “unavailable” rather than locked, or even just use the same error page as the other “no brew” error. I’m not sure we need to tell all viewers that an author is getting DMCA’d (when we aren’t the ones really arbitrating/deciding that)

[calculuschild]

Merging this as a first step toward #3326 . Thanks @G-Ambatte !