Reconsider some aspects of our curent database setup before we fully migrate ORMs

[anemoijereja-eden]

The current database setup for Tux has accumulated some issues over the course of development, which we should consider looking over before fully rewriting the database logic.
Since the migration from Prisma is also likely going to be fairly involved and potentially coincide with migrating prod to local postgresql, it's also the ideal time to make large changes that could require an external migration script.

Issues of note:

• The AFK database enforces uniqueness on user ids, making it work very poorly in multi-guild scenarios
• The starboard and starboardmessage database tables are named in a fairly confusing manner
• the notes table does not seem to actually be used anywhere.
• the overall naming scheme for database tables is not applied very consistently

All of these issues can be resolved without significant cog changes.