Problem

There remain inconsistencies in our module organization after #8346.
For example, the CommonModule (and its packages) were not updated to use the introduced hierarchy system. It also still has instances of legacy registration.
As another example, the organization of elements is inconsistent across modules. Some use an elements sub package while others do not. Some go further with type-based subpackages while others lump them all together.

Solution

This PR resolves these inconsistencies by using the following guidelines:

• Syntax implementations are to be stored in a elements/<type> package, such as elements/expressions or elements/effects. elements is to be placed directly in the package of the module.
• Type classes can be placed in a types subpackage of the module
• EntityData classes can be placed in an entitydata subpackage of the module
• Submodules should be used for "things" that are expected to have multiple syntaxes and/or types around them.
  • Consider PlayerModule in EntityModule or BookModule in ItemModule.

I have also moved some ClassInfo registrations into their modules. This PR also fixes an issue where DefaultFunctions were loaded before modules. This could result in some functions failing to load due to the relevant ClassInfos having not yet been registered.

Testing Completed

There are no tests added as this is simply reorganization.

Supporting Information

n/a

Completes: none
Related: none
AI assistance: none