Feat: Misc Fixes & Recruitment Channel BabySitter

[SimplyJpk]

Description 📝

Fairly basic clean-up of the repo, a number of simple fixes have been applied.

• Added some additional information to the ReadMe regarding Docker and getting the project to run, and remove other misc details that had long since been abandoned.
• Replaced use of Discriminator with DisplayName "NickName (aka Username)" where possible, otherwise use of DisplayName (which will show NickName as preference, with Username shown if no Nick)
• Added some additional checks during database startup to prevent some issues with docker
• Track Deleted and Edited messages better, smaller format, include edited messages if still exists in cached results, but also includes a small message any time a message is edited to maintain proof of change if required.
• Introduced a Bool in the settings to easily enable/disable the previously merged UnityHelp BabySitter service so that if it doesn't work as intended after all this time since implementation, it can at least be disabled without rolling-back.
• Expanded Logger enum to support some of our own Severity types, mostly for debugging but a green "Positive" and a darker yellow "LowWarning" for more ignorable issues.
• Fix issues (hopefully) with the Welcome service
• Add settings for UserRoleService which we don't use so it uses less processing and doesn't latch into more gateway events.
• Added a utility method to see the ID of tags in forum posts so that they're easier to identify. Discord doesn't give us a way to see these without bot assistance.

Big Changes

• RecruitmentService made to babysit the recruitment channel, it opperates under the expectation that deleting messages is fair-game and that failure to meet guidelines is deletable. It follows pretty simple rules, with 2 main regex checks for new threads in the relevant channels.

Match Currency: (?:\$\s*\d+|\d+\s*\$|\d*\s*(?:USD|£|pounds|€|EUR|euro|euros|GBP))
Was Rev-Share mentioned: \b(?:rev-share|revshare|rev share)\b

Rev-Share isn't a "deletable" offense if a price was included in the message, but I feel the notice alone should help guide users to make decisions better. ie; avoid potential rev-share.

I've included some screenshots of basic intended functionality, however the wording of some of these have changed to be more straight forward.

Link to Issue🔗

#212

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
18 Code Smells

0.0% Coverage
0.0% Duplication

[SimplyJpk]

This should be fine to merge, fixs a number of smaller and larger issues. I've made the changes required for the stagging server setting. I'll eventually do another PR with dev into main once we've got a couple people to at least try use the stagging recruitment channel.