Merge devel for pre-release 3

[RobynLlama]

Finally, all our work pays off. This update completely re-writes the deploy strategy of Flowerloader from being the main entrypoint into the program to being split across 3 segments.

The Game Specific Definitions

At the topmost layer: The game definitions define what method is used for logging and hooking into the supported game. The definitions then create layer 2 and supply it with the callbacks needed for logging. This allows games to define what surface is used for logging (if any) and if any other conditions (E.G. a timeout) should occur before hooking is completed. @AlbinoGeek put a lot of work into outlining the way the new system should work, since Typescript definitions still sorta confuse me a little, hehe. Thanks.

The Core

Once the game definitions have had their time to run, they hand off execution to the flowerCore. FlowerCore locates and loads every plugin, passes them the requisite LogSources and organizes the loaded plugin list by reading plugin metadata. It also handles exceptions and issues that arise during plugin loading. It has no concept of what game it is being run in and operates fully independently of the game-specific definitions files. Once its job is complete, all plugins are loaded and ready to operate.

The Patcher

FlowerPatcher is not directly called by any of the other layers, it exists horizontally to flowerCore and simply waits until triggered by plugins requesting a patch be created and applied to an object or method. In many ways, flowerPatcher is the beating heart of flowerLoader as, without it, all plugins would only run static code and responding to game events would be much harder. The majority of plugins will register many patches to achieve their goal.