Protect API endpoints with token auth middleware

[cameronkinsella]

Protects most endpoints with token auth. The only endpoints not protected are the ones required for login, where the user does not yet have an auth token.

Since endpoints now require authentication, you will need to add a Bearer Token type Authorization header if you are testing endpoints in something like Postman. To obtain a token, you can:

1. Click the Copy Token button while logged in as an admin (dev or prod).
   
2. Copy the token that is created and logged when the backend server starts (dev only).
   
3. Copy the value of your jwt cookie while logged in as an admin (dev or prod)
   

The token auth verifier will check for both cookie or bearer token, so if you are already logged in as an admin then you can access GET endpoints just by visiting their URL.

The following frontend functionality has been tested and is not broken:

• Create user
• Delete user
• Add new key
• Revoke keys
• User registration
• User login/logout
• Create/Edit role
• Update user roles
• Door auth with passkey

[cameronkinsella]

Added a settings modal. It can be opened by clicking on the cog icon on the top right. It currently only contains the logout option and (if the user is an admin) the option to copy their access token. Feel free to adjust the look and feel of these components.

I also added a disclaimer to educate the user about misuse of the access token. They must acknowledge this disclaimer before they are able to copy the token. The disclaimer is a bit long, so it becomes scrollable if the max height for it is reached.

output.mp4

[AdrianJendo]

Added a settings modal. It can be opened by clicking on the cog icon on the top right. It currently only contains the logout option and (if the user is an admin) the option to copy their access token. Feel free to adjust the look and feel of these components.

I also added a disclaimer to educate the user about misuse of the access token. They must acknowledge this disclaimer before they are able to copy the token. The disclaimer is a bit long, so it becomes scrollable if the max height for it is reached.

output.mp4

I'm not going to approve this. I don't think this is good UI / UX and adding this token does nothing beneficial for our symposium.

[cameronkinsella]

Reverted settings modal and moved the access token dialogue to replace the logged in admin's self-delete button.
The button works the same as the video above.

[AdrianJendo]

Is "Settings" the correct title? Also I don't think the brackets are necessary

[cameronkinsella]

Changed the title to "Warning". The brackets on Confirmation are necessary because content expects an Element and Confirmation is () => Element.