Add a tracked data handler registry

[haykam821]

This pull request introduces a new API for registering tracked data handlers, which reduces conflicts between mods registering tracked data handlers in an order that is inconsistent between clients and servers.

To use the API, simply replace usages of the vanilla method:

- TrackedDataHandlerRegistry.register(TRACKED_DATA_HANDLER);
+ FabricTrackedDataRegistry.registerHandler(TRACKED_DATA_HANDLER_ID, TRACKED_DATA_HANDLER);

An example of a mod introducing tracked data handlers is provided within the test mod. This entity uses tracked data handlers for global positions, items, and optional item groups, all of which are not available as one of the vanilla tracked data handlers.

A few remarks regarding the implementation of this API:

• Documentation has not been written yet.
• Note that the class name is FabricTrackedDataRegistry rather than FabricTrackedDataHandlerRegistry so that tracked data support can be added in the future within the same class; see #1049 for more information.
• Each registration recomputes the map used by vanilla. I'm not sure whether optimizing this behavior is worthwhile; the work required to delay computation until the map is accessed would be more invasive than the current setup.
• Mods that do not switch to this API will still work as before. Said mods will not gain the benefits of using this API and will still lack a guarantee of tracked data handlers matching between clients and servers.
• There isn't any guard against registering a tracked data handler after mod initialization. Should one be added? Currently, the unspoken idea is that mods will only use this API during mod initialization.
• Mods assuming that tracked data handler IDs are stable during mod initialization (or possibly later, per the last remark) will be broken. I assume this breakage is fine, as I doubt many mods interact with tracked data handlers in this way.

Fixes #3482

[Linguardium]

would it be beneficial to add a warning if a non-vanilla handler is registered? (outside of the api)

[haykam821]

@Linguardium A warning already will be logged in that scenario.

[Linguardium]

Yep, i missed that

[modmuss50]

@haykam821 are you intrested in finishing this off? I dont think there was anything too crazy left to do on it.

[PepperCode1]

Superseded by #4599.