fix(coroutines): swallowed exception in global scopes

[MukjepScarlet]

No description provided.

[liquidbounce-support-bot]

Thanks for this — centralising the handler is a clear win over the two lambdas that silently dropped everything that was not a ReportedException, and the clientLogger("ChunkScanner") / withFormat() cleanups are nice.

A couple of things worth a second look before merge:

• ModuleMobOwners now launches the Mojang lookup on Dispatchers.Main, where it previously ran in ioScope (Dispatchers.IO). If the suspend call does not dispatch itself off the main thread, that puts a network request on the render thread — was the switch to Dispatchers.Main deliberate (e.g. for the cache write) rather than using IO plus a main-thread hand-off?
• uuidNameCache drops ConcurrentHashMap for a plain hashMapOf, so it is only correct while every read and write happens on one thread (putIfAbsent here resolves to the JDK default, not a CAS). Worth confirming getOwnerInfoText is only ever reached from the main thread.
• ChunkScanner.scope becomes private — fine as long as nothing outside the object (or an add-on) referenced it.
• Style: override val key on CommonCoroutineExceptionHandler is redundant, CoroutineExceptionHandler already defines it as its own key.

No documentation impact that I can see.

---

🤖 Automated support reply — a human maintainer will review if this doesn't help.