modules mistakenly placed in engine namespace

[keturn]

#4560's migration was applied too broadly and ended up moving some packages in modules instead of just the engine, as in Terasology/Inventory#38

Fixing this doesn't involve changes to the Terasology repo, but an issue here next to #4560 seems a good a place for a tracking issue as any.

Edit: Usurped by #4580 I guess?

[keturn]

There aren't too many of these modules in omega that ended up containing a package org.terasology.engine statement:

• Compass
• CoreWorlds
• Health (I thought I caught this one! Guess not.) - see organize under single health package Terasology/Health#71 for desired new organization
• Inventory chore: fix import order and whitespaces Terasology/Inventory#38
• Minimap

but references to some of those like Health and Inventory will have leaked to a lot of dependent modules.

[keturn]

I think the plan for fixing this is:

1. Decide whether, since we need to correct references in all the dependent modules anyway, we want to make other intentional changes to the namespace of these modules while we're at it. Some discussion of this in organize under single inventory package Terasology/Inventory#37
2. Make a migration file that explicitly lists each class being moved. Doing recursive migration of packages is how I got us in to this mess!
   • we could migrate packages iff we can confirm that there are not multiple projects adding classes to that package, but once we've started bulk-listing classes it sounds easier to just stick with classes than do that confirmation.
3. Apply the migration to all omega modules.

[keturn]

usurped by #4580