Refactor existing lifecycle into a more modular PluginModule

[Infinitay]

This PR is an attempt to better modularize my existing codebase and plugin lifecycle by using abstraction and primarily constructor injection. The few benefits to this refactor are:

• Cleaner codebase
• Better defined plugin lifecycle
• Better dependency injection handling
• Re-post various game events which will eliminate the need to manually refetching the required data on cold starts (with the exception of a few events such as Varbits)

Events Implemented and Tested

• Beekeeper
• Capt' Arnav's Chest
• Drill Demon
• Freaky Forester
• Gravedigger
• Maze
• Mime
• Pinball
• Sandwich Lady
• Surprise Exam
• Quiz Master

feat(module): Created PluginModule class for modular plugin lifecycle

• Created an abstract class PluginModule to better handle multiple modules within the plugin and to appropriately handle the lifecycle
  • Construct injected common fields such as OverlayManager, Client, and the config
  • Field injected on-demand fields such as EventBus and GameEventManager
  • Automatically (un)registers the module from the EventBus
  • Re-fire various events by utilizing GameEventManager#simulateGameEvents within #startUp
  • Abstracted #onStartUp to handle module starts, #onShutdown to handle module stops, and #isEnabled to determine the status of the module

[Infinitay]

feat(module): Created PluginModule class for modular plugin lifecycle

• Created an abstract class PluginModule to better handle multiple modules within the plugin and to appropriately handle the lifecycle
      - Construct injected common fields such as OverlayManager, Client, and the config
      - Field injected on-demand fields such as EventBus and GameEventManager
      - Automatically (un)registers the module from the EventBus
      - Re-fire various events by utilizing GameEventManager#simulateGameEvents within #startUp
      - Abstracted #onStartUp to handle module starts, #onShutdown to handle module stops, and #isEnabled to determine the status of the module

refactor: Start refactoring RandomEventHelper to modular plugin lifecycle

• Removed prior injections that have yet to be refactored
• Refactored #startUp, #shutDown, and #onConfigChanged to utilize the new modular system to handle state changes

refactor(surpriseexam): Migrate SurpriseExamHelper to PluginModule lifecycle

• Refactored SurpriseExamHelper to the modular plugin lifecycle
  • Now extends PluginModule and implements respective methods, moving the existing start/stop login there
  • Use constructor injection and removed duplicate field injections
• Injected SurpriseExamHelper and added it to the pluginModulesMap

feat(PluginModule): Add #isLoggedIn to check if the player is logged in

feat(surpriseexam): Improve support for starting during active event

• Improved handling initial runs when (re)starting the plugin when already inside the Surprise Exam random event
  • Primarily for when the puzzle interface is already on screen

[Infinitay]

refactor(captarnav): Migrate PirateHelper to PluginModule lifecycle

• Refactored PirateHelper to the modular plugin lifecycle
  • Now extends PluginModule and implements respective methods, moving the existing start/stop login there
  • Use constructor injection and removed duplicate field injections
• Injected PirateHelper and added it to the pluginModulesMap

refactor(mime): Migrate MimeHelper to PluginModule lifecycle

• Refactored MimeHelper to the modular plugin lifecycle
  • Now extends PluginModule and implements respective methods, moving the existing start/stop login there
  • Use constructor injection and removed duplicate field injections
• Injected MimeHelper and added it to the pluginModulesMap

feat(mime): Improve support for starting during active event, overlay, refactor

• Improved handling initial runs when (re)starting the plugin when already inside the Mime random event
  • Primarily for when the emote button interface is already on screen
• Change Mime text when undetermined emote answer
• Use default font size for overlay
• Refactored Mime animation checks and answer updating into #updateMimeAnimation

[Infinitay]

Note, while testing the Mime module, I noticed that starting and stopping the refactored Gravedigger module (multiple times) seems to have overlay issues again when switching back to field injection for both overlays.

[Infinitay]

refactor(drilldemon): Migrate DrillDemonHelper to PluginModule lifecycle

• Refactored DrillDemonHelper to the modular plugin lifecycle
  • Now extends PluginModule and implements respective methods, moving the existing start/stop login there
  • Use constructor injection and removed duplicate field injections
• Injected DrillDemonHelper and added it to the pluginModulesMap

feat(drilldemon): Improve support for starting during active event

• Improved handling initial runs when (re)starting the plugin when already inside the Drill Demon random event
  • Fix race condition issue with events - primarily regarding #onGroundObjectSpawned and exerciseMatsMultimap

---

It's probably better to have kept the varbit initialization within #onNpcChanged, but I wanted to keep everything inline for the future. I want to handle varbit inits #onStartUp. Though looking back, I may have to reconsider this due to the way GravediggerHelper is implemented. Also, it does spam the log with 4/8 writes due to the varbit value being 0 and reaching

Random-Event-Helper/src/main/java/randomeventhelper/randomevents/drilldemon/DrillDemonHelper.java

Lines 235 to 248 in 773da8d

	private void updateExerciseMappings(int exerciseVarbitValue, int postNumber)
	{
	DrillExercise exercise = DrillExercise.VARBIT_TO_EXERCISE_MAP.get(exerciseVarbitValue);
	if (exercise != null)
	{
	log.debug("Drill Demon exercise of Post_{} changed to: {} ({})", postNumber, exercise.getVarbitValue(), exercise.name());
	this.exerciseVarbitMatMultimap.replaceValues(exerciseVarbitValue, this.exerciseMatsMultimap.get(postNumber));
	}
	else
	{
	log.warn("Drill Demon exercise varbit changed to unknown value: {}", exerciseVarbitValue);
	this.exerciseVarbitMatMultimap.replaceValues(exerciseVarbitValue, ImmutableSet.of());
	}
	}

The log being log.warn("Drill Demon exercise varbit changed to unknown value: {}", exerciseVarbitValue); , but that's expected because of how Jagex inits the varbs to 0. I could just ignore it, but I think it'd be better to just have it for now.

[Infinitay]

refactor(beekeeper): Migrate BeekeeperHelper to PluginModule lifecycle

• Refactored BeekeeperHelper to the modular plugin lifecycle
  • Now extends PluginModule and implements respective methods, moving the existing start/stop login there
  • Use constructor injection and removed duplicate field injections
• Injected BeekeeperHelper and added it to the pluginModulesMap

feat(beekeeper): Improve support for starting during active event

• Improved handling initial runs when (re)starting the plugin when already inside the Beekeeper random event
• Avoid constantly appending corresponding number to destination widget label

[Infinitay]

feat(captarnav): Improve support for starting during active event

• Improved handling initial runs when (re)starting the plugin when doing Capt' Arnav's Chest random event
• Add missing isSolved = false assignment within PirateChestSolver#isChestCorrectlySet