Backend: Allow Parameterless Handling of SkyHanniEvent(s)

[DavidArthurCole]

What

For the cases where @HandleEvent is needed solely as the starter for a code snippet, where the normal event: ... function construction would warn about an unused param.
Probably the most divisive PR I've opened :D

Images

Changelog Technical Details

• SkyHanniEvents can now be @Handle-d without an event: parameter. - Daveed
  • New alternate annotation is @HandleEvent([ClassThatExtendsSkyHanniEvent]::class).

[github-actions]

I have detected some issues with your pull request:

Body issues:
Author is not set in text: + SkyHanniEvents can now be @handle-d without an event: parameter.
Change should start with a letter instead of a number or special character in text: ``SkyHanniEvents can now be @Handle`-d without an `event:` parameter.`
Extra info without a change in text: ` * `@HandleEvent(eventType = [ClassThatExtendsSkyHanniEvent]::class)`.`

Please fix these issues. For the correct format, refer to the pull request template.

[github-actions]

One or more Detekt Failures were detected:

• EventListeners.kt#L20: Too many throw statements in the function addListener. The maximum number of allowed throw statements is 2.
• EventListeners.kt#L35: Line detected, which is longer than the defined maximum line length in the code style.
• EventListeners.kt#L35: Use require() instead of throwing an IllegalArgumentException.
• EventListeners.kt#L40: Use require() instead of throwing an IllegalArgumentException.
• EventListeners.kt#L47: Use require() instead of throwing an IllegalArgumentException.