Add Thread Naming Support

[jdrueckert]

Motivation

Parallelization is nice for performance, but can complicate debugging if things go wrong.
Ideally, all our threads should have names to help us during debugging to figure out which kind of tasks are executed on a specific problematic (hanging, failing, ...) thread.

With our previous mechanisms for parallelization, i.e. the ThreadManager, it was possible to provide a name when submitting a task:

engine.getFromEngineContext(ThreadManager.class).submitTask("loadGame", () -> {...})

With the currently ongoing transition to Reactor, the question is, whether RxJava provides a similar concept.

Proposal

@keturn mentioned:

there is a subscriber Context that is useful for things like this.

and

#4839 added a GameScheduler::scheduleParallel method that takes a name which it uses in the same way as ThreadManager::submitTask did. It doesn't address future use cases where we take advantage of Flux's model for pipelines, but it suffices for one-shot Runnables like this.

Additional notes

Related PRs & Issues:

• chore(RegisterMods): make sure thread has a name and is set to daemon #4547
• refactor(GameScheduler): provide ThreadMonitor-compatible schedule method #4839
• refactor: replace usage of ThreadManagerSubsystem with reactor Scheduler #4799

[DarkWeird]

We have code for resolve this issue...
But i wrote it in #4865
See GameScheduler.java and any usage

[skaldarnar]

@DarkWeird That's great, and definitely something we overlooked!

Maybe we can take out (some of) the changes to GameScheduler into a smaller PR and get that merged separately. Then we can most likely call this done pretty fast.