Add lock routes

[G-Ambatte]

This PR contributes towards Issue #3326.

This PR adds the following routes to the Admin API:

• /admin/lock : GET returns the number of documents in the collection that have the lock.locked property set to true.
• /admin/lock/:id : POST takes a brew ID and a JSON lock object; updates the identified brew with the properties of the lock object.
• /admin/unlock/:id : PUT takes a brew ID; removes the lock from the identified brew
• /admin/lock/reviews : GET returns a collection of documents that has the lock.locked set to true and lock.reviewRequested exists.
• /admin/lock/review/request/:id : PUT updates the identified brew's lock object with a reviewRequested property (current date/time). NON-ADMIN ROUTE
• /admin/lock/review/remove/:id : PUT updates the identified brew's lock object to remove the reviewRequested property without removing the entire lock.

[5e-Cleric]

We could use two columns in the lock tab there

Attaching screenshot for reference

[G-Ambatte]

Still working on functionality, visibility will come next.

[G-Ambatte]

On opening a locked brew for editing:

On clicking "REQUEST REVIEW":

On the new "LOCKS" tab of the Admin page:

• Lock Count:
  
  Clicking "REFRESH" causes the lock count function to run and update the total.

• Brews Awaiting Review:
  
  Clicking the button causes the locks with review function to run and update the table. Clicking a row in the table causes the Share ID to be copied to the clipboard (NYI: words explaining this on the page).

• Lock Brew:
  
  The four fields are required, attempting to submit a lock with an empty field results in the following:
  
  The information on the right are suggested codes (from this Github comment and information about the messages

• Unlock Brew:
  
  Entering the Share ID of a locked brew and clicking the button results in the lock being removed from that brew, if one exists.

• Clear Review Request
  
  Entering the Share ID of a locked brew and clicking the button results in the review request being removed from a locked brew. Possibly this should also have an option to update the editMessage to advise the user why their changes are insufficient to have the lock completely removed.

[G-Ambatte]

Still need to implement some feedback from the Lock Brew method, to indicate success or failure. Otherwise I think most of the functionality is in a good place, although the styling could probably still use some improvement.