feat: add per-category blocked roles-list

[itzwam]

Versioning information

• This includes major changes (breaking changes)
• This includes minor changes (minimal usage changes, minor new features)
• This includes patches (bug fixes)
• This does not change functionality at all (code refactoring, comments)

Is this related to an issue?

Changes made

Added per-category roles blocklist

Confirmations

• I have updated related documentation (if necessary)
• My changes use consistent code style
• My changes have been tested and confirmed to work

[eartharoid]

@itzwam how would you use this feature?
The uses I'm thinking of can be fulfilled by required roles.

[itzwam]

Late reply cuz I didn't see your message,

on my side there are some ticketing categories that are allowed for all roles
except a specific one, and I would try to avoid allowing manually all roles for the evolutivity of the solution

let's say I create 12 roles on my server, I dont want to update the allowed-list with every-roles-but-one, instead I'prefer to specify a blocked role and it works perfectly

that's a workflow I already use locally and I would like to upstream this change to the bot cuz I don't think I'm the only one who needs it

[itzwam]

Just figured-out the DB migrations I edited aren't the good ones, think I will need to create new schema migrations files for this specific upgrade, but not sure how to do it properly

it "worked" like that but pretty sure I'm not supposed to edit old schema migration scripts.

[eartharoid]

Yes, the SQL files should be reverted.
The process for generating new migrations is to use primsa migrate dev for each of the providers.

[Owned67]

we need to apply change on files and restarting bot or a bit complicated for apply this change? thx

[itzwam]

Removed schema migrations + squashed things

will try to run primsa migrate dev on my side