Implement global blocklist

[No767]

Summary

This PR focuses to implement a global blocklist. When an user is blocked by the bot, all tickets and access to the bot is nullified. For prefixed commands/messages, no response will go to the ticket and no response from commands will be sent back. For app commands, an ephemeral message is sent denoting that the user is blocked. Mods can either manually remove users from the blocklist manually or have it automatically removed after an desired amount of days. Hierarchy and permissions are factored into this process.

For simplicity and practicality purposes, the blocklist will only accept members, not roles. Modmail accepts both, but in the context of the transprogrammer server, it's too risky allowing roles to be blocked and each user isn't tied to an specific role. As the server has roles for a wide variety of labels, blocking one role just because of one user is in that role makes no sense.

Before this PR can be merged, a wide variety of tasks need to be completed. These are noted as the following:

• Adding hierarchy checks for EntityConverter
• Block for processing any further tickets
• Check if the command execution timestamp is less than the expiration timestamp for config blocklist remove
• Implement timer mechanism (either Sinbad's or R. Danny's) for automatically removing users off of the blocklist
• Ensure to lock the ticket once an user has been added to the blocklist (if the user has any ticket at all)

Note: The timer and all other improvement features are slated to be implemented in another PR. This PR solely aims to provide the base implementation of the global blocklist system

Types of changes

What types of changes does your code introduce to Rodhaj
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes. (if appropriate)
• All workflows (except pre-commit.ci) pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarcloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud