[Feature / Cleanup] Sign rework (WIP)

[DerToaster98]

Describe in detail what your pull request accomplishes

This PR is a attempt at redoing signs in a more organized way.
That encompasses the following things:

• Signs get registered to a central registry / map
• A single listener retrieves the fitting registered sign and calls those for processing
• Signs can be overridden, useful for addons that want to change behaviors of let's say move signs (e.g. Squadrons reloaded)
• Removes redundant code and should make it cleaner
• Should make remote sign implementations much cleaner cause that way one can just call the relevant registered sign instead of firing a new event

TODO List:

• Base class for signs
• Base class for "craft signs" (everything that requires a craft and that can react to craft detection and sign translation)
• Sign registration
• Sign retrieval by "ID"
• Base cruise sign
• Base information sign
• AbstractCruiseSign => will be the base class for signs acting similar to the cruise sign
• Abstraction layer for signs
• 1.20+: Support for sided signs
• Deprecation notice and comment in all relevant places that use the SignWrapper as discussedin Change SignTranslateEvent to use Adventure #688
• Change SignTranslateEvent to use the SignWrapper
• Subcraft base sign
• Re-Implement existing signs
  • Ascend sign
  • Descend sign
  • Cruise sign
  • Helm sign
  • Name sign
  • Move sign
  • Pilot sign => TODO: Should we replace the PilotValidator in the detection task or not?
  • RelativeMove sign
  • Release sign
  • Remote sign => will receive rework to better handle multiple target signs and to avoid beavering => Not possible without rewriting how the release stuff works
  • Scuttle sign
  • Speed sign
  • SubcraftRotate => will maybe receive a rework so it is more reliable and less prone to beavering
  • Teleport sign
  • Status sign
  • Contacts sign
  • [ ] NEW Subcraft Move Postpone for later, this requires thorough analysis prior

Checklist

• Proper internationalization
• Tested
• Performance tested (could improve performance on remote signs and subcraft, not done yet)

[TylerS1066]

  * [ ]  **NEW** Subcraft Move

This would be best left for a separate PR. I believe there are many assumptions that Subcrafts never move, so we'll have to do a through review of the codebase for that feature.

[DerToaster98]

  * [ ]  **NEW** Subcraft Move

This would be best left for a separate PR. I believe there are many assumptions that Subcrafts never move, so we'll have to do a through review of the codebase for that feature.

Alright, i will remove that from the todo list. Will implement the other points nonetheless