Top-level registry package

[haykam821]

Since tags are greatly tied to registries now, it would be ideal to restructure registries to have a more promenient top-level package, like tags already do.

Here's a potential structure:

• net.minecraft.registry
  • The Registry class and its subclasses
  • .tag
  • .entry
• net.minecraft.world
  • The DynamicRegistryManager class

[liach]

imo dynamic registry manager would go to server.registry since it's loaded server-wide

[haykam821]

The dynamic registry manager exists on the client as a destination for synced registries. With this in mind, it could also go into net.minecraft.network.

[liach]

hmm, then imo just putting it in the registry or its subpackages are fine. refer to where we place universal command stuff