Now that the function to INSERT and DELETE from MariaDB is set up, this diff handles setting up the endpoint, responder and validator, as well as the action method that'll be called via
useServerCall client-side.

To not block review while I figure out how to alert the client of a message pin, I've created a follow-up task to decide what to replace Promise<void> with: https://linear.app/comm/issue/ENG-3392/alert-the-client-of-a-message-pin-unpin

Linear: https://linear.app/comm/issue/ENG-3187/set-up-responders-endpoints-and-related-functions-to-toggle-a-message

Depends on D6929

The testing for both the previous diff and this diff are combined here. I tested the stack so far by doing the following:

1. Finding a place to call toggleMessagePin on the client. It's not really important where I call it, just as long as the code runs, so I used the thread settings media gallery on web since it's easy to reach (just need to open the gallery).

2. Log into an admin account locally.

3. Call toggleMessagePin with the following parameters: {messageID: "83806", threadID: "83794", action: 'pin}. I confirm that the message was considered pinned.

4. Call toggleMessagePin with the following parameters: {messageID: "83806", threadID: "83794", action: 'unpin'}. I confirm that the message was considered unpinned.

5. Log into a non-admin account part of a thread

6. Call toggleMessagePin and confirm that the ServerError throws