Adds ping-protection module.

[Kevinking500]

A full module dedicated to protecting specific users/roles for future pings!
Features:

• Sends a notice message with a GIF showing how to disable mention pings, about not being allowed to ping that user/role.
• User is able to configure the warnings message with embed functionality, while also being able to configure the protected roles, users, ignored roles and channels and to allow/don't allow reply pings
• User is able to configure if the bot will log ping history (default, yes and by default stored for 3 months.), if it logs moderation history (default no, as moderation capabilities is by default off. Stored for up to 12 months.) and if it keeps logs of leaved users (by default yes, by default up 1 day after leave, can be up to 7 days.)
• User is able to configure if the bot will mute or even kick the user after they reached xx amount of pings within a timeframe. By default it is 10 pings to trigger action within the configured timeframe of pings history logging. It also has an "advanced" configuration for that to allow for a custom timeframe in weeks. The mute duration can also be adjusted to liking.

Maybe even more features that I forgot to mention here lol
This module has been extensively tested by me and my testers over a 3 day period going over every feature, including after a full code polish. Changes may look longer/shorter in duration between them because I only commit changes once tested it works.

[CLAassistant]

All committers have signed the CLA.

[Kevinking500]

By the way to maybe answer some questions you may have:

• Why did I do select instead of integer in storage.json for database storage duration?

I did select with the specified minimum and maximum amount of storage time to prevent user-side configuration errors

• Why is this not an add-on to the moderation module or ghost-ping module?

This module is supposed to have many configuration fields, options and it wouldn't make sense to put it into a module, additionally I plan to add many other features in the future which would be inlogical to be inside a module

• Why did I not do a command warning for the panel command?

The bot already checks if the executor has administration permissions and the delete data button checks for it again, as the executor is supposed to make it not in a public channel, but sometimes they do and therefore the data deletion button checks it again

Just in case you were wondering any of the above, then you have the answers ^^
(If any of the above require a change let me know)