chore: rename engine-module.txt to module.txt

[jdrueckert]

Resolves #4646

Tbh I have no idea, if this is what's expected to be done to resolve #4646 ...
I just thought I'd go for what I understood and use that as a basis for discussion 🤷‍♀️ 😅

[keturn]

It looks like the one thing you left out of this PR titled "rename engine-module.txt to module.txt" was renaming engine-module.txt. 😜

[jdrueckert]

It looks like the one thing you left out of this PR titled "rename engine-module.txt to module.txt" was renaming engine-module.txt. stuck_out_tongue_winking_eye

Whoops 😅 Should be done now

[keturn]

Ah, now it runs with passing tests!

I see versionInfo.properties is built with version information, and I believe the test cases will make sure that ModuleManager has a module of the appropriate name.

I think that the only thing left to confirm is that you can actually run a game world in a real process with other (non-engine) modules present. Can't think of anything else in particular to look for beyond that.

[pollend]

@jdrueckert do you want to merge this?

[jdrueckert]

@jdrueckert do you want to merge this?

need to test it properly (as keturn mentioned) first, but once that's done: yes.
any objections? @pollend

[jdrueckert]

tests out fine in CoreGameplay, so I'll go ahead and merge this