Prepare modules for implementation of ForgeHooks and co.

[kitlith]

Required for #115. No, this isn't finished, but I figure getting a PR open before I go sleep makes it easier for other people to comment/review what I'm doing.

a note: Glitch said these classes should be named PatchworkEvents, but I went with Events as that was the pre-existing style. I can do a commit to refactor these cases into PatchworkEvents though, so lmk if you'd like me to do that.

Each commit should handle a module, and should be able to be looked at individually.

[kitlith]

okay, that's all the events I found that are called in ForgeHooks, and similar at least. not all of ForgeHooks is sending events though. (i.e. ForgeHooks.canHarvestBlock)

I'm also somewhat dubious about that last commit with patchwork-gui, since those event aren't fired yet, but I decided to go for it since the classes were already present (unlike other methods that I avoided adding because the class was commented out)

[kitlith]

I'm splitting this into seperate PRs.

• patchwork-capabilities (Implement ForgeEventFactory.gatherCapabilities #129)
• patchwork-events-entity (Dispatch to EntityEvents from ForgeHooks, etc. #134)
• patchwork-events-input (Dispatch to InputEvents from patchwork-god-classes #130)
• patchwork-events-lifecycle (Dispatch to LifecycleEvents from patchwork-god-classes #128)
• patchwork-events-world (Dispatch from ForgeHooks to WorldEvents #133)
• patchwork-gui scratch that, the events aren't implemented yet, i'll just leave this to whomever actually implements them.