Implement core tickets system

[No767]

This PR addresses #8, #10 and #19 . The features being implemented are the following:

• Ticket creation and lifecycle
• User webhook replying back in the ticket forum
• Staff notifications/logging for ticket creation and closure
• Ticket closure command
• Basic info and active commands for users
• Replying back as an admin back to the user in thread

And there are changes to views as well. In addition, there are some remaining tasks that needs to be addressed before this PR can get reviewed and merged, notability:

• Replying back to the user from an admin
• File attachment support for tickets
• Implement basic info and active commands
• Temp cache and selection process of tags
• Allow for custom user titles (w/ defaults?)
• Cleaner implementation of the ?close command
• Remove the notification system as this may stress folks more
• Implement proper logging w/ embeds (such as when a ticket is created and closed) - But how would this information be used to plan rational decisions in the future?

And some bugs that needs to be ironed out:

• Ticket Creation View keeps on editing an unknown message
• Caches not being properly invalidated

[sonarcloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

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

See analysis details on SonarCloud