add Translation::GenerateName()

[myk002]

Also available from Lua as "dfhack.generateName(...)"

Fixes: #5166

[myk002]

Would it be feasible to provide an additional signature of dfhack.GenerateName(name, language, type) that chooses appropriate selectors based on the language_name_type? I can write the LuaApi glue if you write the cpp.

[quietust]

There is no single set of rules for how the major/minor selectors are chosen - sometimes they're taken from the global list and sometimes some are taken from the entity definition, and sometimes it uses the major/minor selectors and sometimes it uses the major selector both times.

[lethosor]

I had a naming suggestion on Discord. Not sure if it's worth implementing here or not.

I've felt for a long time that we ought to move this stuff to a dfhack.translation module, to match C++
we could alias the old dfhack.TranslateName = dfhack.translation.translateName or something like that, and make the case in the new API consistent with the other APIs

[myk002]

Could you resolve the changelist conflicts? It seems like I can't push updates to your branch

[myk002]

I've felt for a long time that we ought to move this stuff to a dfhack.translation module, to match C++
we could alias the old dfhack.TranslateName = dfhack.translation.translateName or something like that, and make the case in the new API consistent with the other APIs

captured in #5180

[quietust]

I've confirmed that the function works correctly from C++ (the StrangeMood plugin successfully generated the artifact name "Mosusthilség", "Roomtarnished"), and it also seems to function correctly from Lua if you provide the correct parameters (I ran dfhack.GenerateName(name, 0, df.language_name_type.Artifact, df.global.world.raws.language.word_table[0][1], df.global.world.raws.language.word_table[1][1]) and got reasonable-looking names).