Create invite tRPC procedures

[L-Mario564]

For each procedure:

• Apply rate limit middleware.

All inputs listed are required/must be defined unless stated with ? appended at the end of the variable name.

Cancel invite

Update Invite.status to cancelled.

Input: inviteId.

Conditions

• The invite's byUserId must be of the session user.
• Invite status should be of status pending.

Reject invite

Update Invite.status to rejected.

Input: inviteId.

Conditions

• The invite's toUserId must be of the session user.
• Invite status should be of status pending.

[ArtemOsuskyi]

No accept invite?

[L-Mario564]

Accepting an invite will perform different operations on the backend and database depending on the type of invite that's being accepted, so those procedures will live in under the router where they make most sense. For example, the procedure for accepting a staff team invite will add that user to the tournament's staff team so it'll go under the staff members router.

[ArtemOsuskyi]

Need a procedure to get all user invites as well probably @L-Mario564

[L-Mario564]

Need a procedure to get all user invites as well probably @L-Mario564

Don't think a procedure is necessary, unless you're seeing a use case where they could be fetched from two or more parts in the codebase?