[PATCH] Rename TechnologyTemplateManager to JsonTemplateManager

[sanderd17]

Since the TechnologyTemplateManager doesn't only do techs anymore, it should be renamed to something more generic, like JsonTemplateManager.

Note: this also disables serialization of the cached tech data (refs #3834 )

Due to the difficulty of renaming files and creating diffs of those, I've included two patches. They're the same with the exception that one has renamed files and the other one doesn't.

[sanderd17]

Note from leper: jsonTemplateManager isn't a good name either (data can contain any data format). Better is something like dataTemplateManager.

[Itms]

I agree with the naming CCmpDataTemplateManager.

Why do you change the function name in TechnologyManager? After all it is still the technology manager so GetTechnologyTemplate is not an inaccurate name.

[sanderd17]

In 18100:

Rename TechnologyTemplateManager to DataTemplateManager in order to reflect its new function. Fixes #3909. Disable serialisation of technology templates. Refs #3834

[elexis]

Since it wasn't linked here yet, it was broken because the Auras and TechnologyManager components still serialized the objects from the DataTemplateManager, thus yielding different backrefs for rejoined clients, thus OOS deluxe (not even visible in the textual dump diff), see #4239.

The component should be a globalscript, so that it can be used by the AI, GUI and rmgen as well.

I initially agreed with JSONTemplateManager so that we immediately know how its different from the TemplateManager. But even better would be splitting the file into an Aura and a Technology file.