Split engine to subsystems

[DarkWeird]

Extraction subsystems should:

1. simplify codebase via extracting common components
2. make some components optional/replaceable. e.g:
   Optional: Telemetry and Discord not needs for server build
   Replaceable: AudioLwjgl and AudioNull subsystems.
3. provide native library support for modules. e.g:
   Kallisti -> Jnlua
CoreRendering -> GraphicsLwjgl

Extraction subsystems shouldn't:

1. Replace Modules
2. Downloads from server or internet
3. Loads dynamically

Draft extraction scheme:

Disclaimer: some listed subsystem is just library - haven't EngineSubsystem implementation. but i cannot place it at libs directory, because libs directory used for external libraries (external repo)

Subscribables is timed subsystem. while AutoConfigs will not extracted and configs not migrated to autoconfigs

Required Features:

1. feat: Reviving of "UI for editing arbitrary types and AutoConfigs" #4244 - for autoconfig. it ideally config system for subsystem ecosystem. needs 7 and 2.
2. Module -> Subsystem dependency.
   Partial current solution for 'Library' subsystems - engine provides them as gradle's api dependency (formal it is engine dependency)

Extractions

1. ✅ DiscordRPC subsystem feature(subsystems): extract DiscordRPCSubSystem #4233
2. ✅ TypeHandlerLibrary feat(subsystems): extract TypeHandlerLibrary. #4255
3. ✅ Add generic Serializer for TypeHandlerLibrary feat(TypeHandlerLibrary): Add generic Serializer for TypeHandlerLibrary. #4324
4. extract EntitySystem. ( requires ✅ feature(subsystem-prepare): extract Network and R&R code from EventSystemImpl #4565 for pure events and ✅ feat(TypeHandlerLibrary): Add generic Serializer for TypeHandlerLibrary. #4324 for serialize components)
5. protobuf serialize over GenericSerilaizer(3)
6. network subsystem - needs 4
7. GsonSerializer feat(subsystems): Extract GsonSerializer #4270 - needs 2.( follow-ups - migrate engine's code from pure Gson to GsonSerializer) Outdated with feat(TypeHandlerLibrary): Add generic Serializer for TypeHandlerLibrary. #4324
8. extractTypeWidgetLibrary -- but first needs to merge feat: Reviving of "UI for editing arbitrary types and AutoConfigs" #4244 ✅
9. extract AutoConfigs - needs 7.
10. extract Audio(Null|API|Lwjgl) subsystems. required .
11. extract Graphics - required AutoConfigs as subsystem and migrated Rendering configs to AutoConfig.
12. extract Record&Replace - highly integrated in engine. needs refactor WorldStorage to make it extendable.
13. ???
14. PROFIT!

[jdrueckert]

In Discord @DarkWeird mentioned the following configs that will need to be migrated to AutoConfig:

• audio
• system
• player
• permission
• input
• binds
• rendering
• defaultModSelection
• worldGeneration
• moduleConfigs
• network
• security
• nuiEditor
• selectModulesConfig
• identityStorageService
• telemetryConfig
• universeConfig
• webBrowserConfig

[Cervator]

Small note:

Optional: Telemetry and Discord not needs for server build

Discord: correct. Telemetry: want! Great way to send server logs and performance. There are client specific bits to the telemetry system though, like blocks broken and such. That part we could certainly skip, but then I'm not sure if that would enable by default 🤔

[DarkWeird]

Investigation of possible to extract AutoConifg as Subsystem:

1. Context should be extracted (feat(extract-subsystems): extract Context, @In, InjectionHelper and @Share to Subsystem #4930) - AutoConfig injects Autoconfigs to context and have @In Injects
2. AutoConfigScreen - takes ModuleManager(engine) and CoreScreenLayer(engine)
   3.AutoConfigWidgetFactory - takes ModuleManager(engine) and TranslationSystem(engine)
3. ColorConstraintWidgetFactory - takes CieCamColors(engine, used for ColorWidget and PlayerConfig also useless ColorHueAnimator), TextureUtil(engine, for color uri) and Texture(engine, loading asset)
4. LocaleConstraintWidgetFactory - takes SimpleUri(engine, can be replaced with ResourceUrn(gestalt)) and TranslationSystem(engine)
5. AutoConfig - takes SimpleUri(engine, can be replaced with ResourceUrn(gestalt)
6. AutoConfigManager - takes Context(engine, subsystems:Context on the way), SimpleUri(engine), PathManager(engine, for save and loading), ModuleManager(engine, can be replaced with directly ModuleEnvironment(gestalt-module)) and ReflectionUtil(engine, resolve SimpleUri from config class and ModuleEnvironment(module-gestalt)))

Possible bonus. if we extract saving and loading from AutoConfigManager then per-game-saves will easier.(PathManager)

Think to do:

1. extract Context (feat(extract-subsystems): extract Context, @In, InjectionHelper and @Share to Subsystem #4930)
2. extract TranslationSystem (there have Translator(nui). but we needs getProject method.. which don't in traslator) or do TODO there
3. replaces SimpleUri with ResourceUrn (partially)
4. idk what to do with CieCamColors(engine)
5. idk what to do with Texture and TextureUtil
6. Idk where move ReflectionUtil.getFullyQualifiedSimpleUriFor(engine). because AutoConfig is single user... but Yet Another ReflectionUtl.... (we have it in TS, in NUI)