leetcode leaderboard page

[adarshm11]

Summary

This PR includes a page and API for managing the LeetCode Leaderboard (sign2) from Clark.

Features

• The leaderboard management page can be accessed from the admin navbar. Officers and admins can add/remove users, and view a preview of what the leaderboard currently looks like.
• The API includes routes to add, delete, and fetch all users, as well as utility functions to perform these actions on the actual sign2 server.
• Unit tests are included - however, these only test that the API routes behave correctly regarding JWT authentication, and does not test the routes' behavior with actually performing requests to sign2. This is because the sign2 connection is behind a gateway controlled by config.json, where users can set whether it is enabled or not. In the future, further unit tests should be added to address these conditions.

Testing

This feature has been tested on the production server, where all functions work correctly. Ensure that, after merging, the sign2-specific data in /api/config/config.json matches what is expected to make sign2 reachable from Clark.

[n8thantran]

lgtm

[evanugarte]

this pr could probably be way less code, see comment

[evanugarte]

i think this file could be even less

like

app.route('/:id')
  .get((req, res) => {
    const userId = req.params.id; // Access dynamic parameter
  })
  .post((req, res) => {
    const userId = req.params.id;
  });

you could probably make a single callback, and pass it in to both .get and .post

like

function idk(req, res) {
  // ...
}

app.route('/users/:id')
  .get(idk)
  .post(idk);

change :id with :path or something

[evanugarte]

do we need this code still, if we have the router.use

does router.use take care of all this stuff now

[adarshm11]

we can do it like this but it doesn't seem aesthetically pleasing to me, thoughts