Potential hard-locking for Tracked Data Handlers

[OroArmor]

Describe the bug

A combination of mixin ordering (we are added after another mod) plus the mod causing the issue not being the development mod could hard lock a game by crashing on startup.

In addition, if a mod injects at the top of <clinit> and registers null, we then believe that is the BYTE handler, causing another crash.

How did QSL break?

quilt-standard-libraries/library/entity/entity_extensions/src/main/java/org/quiltmc/qsl/entity/extensions/mixin/networking/TrackedDataHandlerRegistryMixin.java

Lines 139 to 141 in cbd35a1

	if (!quilt$pastStaticInit && QuiltLoader.isDevelopmentEnvironment()) {
	throw new RuntimeException("Unnamed TrackedDataHandler added before static initialize completed. This either means that a new TrackedDataHandler was added by Minecraft, or a mod injected into a poor place.");
	}

Which environment did you encounter this bug in?

Both

Logs

No response