Feat: Add slash command to generate application form for various community roles

[christolis]

Closes #1024.

Screenshots

Configuration changes

Property	Description	Type	Default
applicationForm.applicationChannelPattern	Where submitted applications end up.	String	"applications-log"

TODO

• Add a 5 minute cooldown per member for sending applications to prevent spam (feel free to recommend alternatives).
  • This could be done by having a HashMap<Member, OffsetDateTime> where the key is the Member who sent an application and the value is the date and time that they sent it. There should be a condition every time a Member attempts to send any application which utilizes the aforementioned HashMap to prevent spam.
• Add JavaDocs for every method where it's necessary.
• Switch to EntitySelectInteractionEvent for the dropdown menu. (EDIT: Impossible since this would forcibly include all existing roles)
• Move selectable roles from the config to the command parameters in a similar fashion with previous commands.
  • This eliminates emoji/description metadata as well that was previously defined in the configuration file.

[Suleman70]

Can i be assigned to this?

[Taz03]

branch update is required, it is using removed APIs

[christolis]

Marked PR as draft since there needs to be some rework on certain things which will be specified in the TODO.

[ankitsmt211]

@christolis what happens to the generated form after x user applies through form? Does the form need to be re-created? Or is it only unavailable for x user to a certain time period?

Also how do we update the form if need be?
Delete message and recreate?

[christolis]

@christolis what happens to the generated form after x user applies through form? Does the form need to be re-created? Or is it only unavailable for x user to a certain time period?

Also how do we update the form if need be? Delete message and recreate?

The generated form is persistent and used by everybody. It does not need to be recreated by whoever has the MANAGE_ROLES permission. As for updating it, that's right. Currently, the way it is developed, the message has to be deleted and get the command executed again, which is not that big of a problem considering the rarity of updating such form.

[surajkumar]

Great PR and the thought put into the development of the feature is evident.

Please can you look into the comments, additionally, there are some duplicate checks happening e.g. multiple guild == null checks. This can be done once much earlier and then you don't have to worry about it.

[tj-wazei]

LGTM!

[SquidXTV]

Thanks for your effort <3