Wonder victory timeout and last man standing checkbox

[elexis]

These gamesetup options new in alpha 21 should become settable in atlas.

[Sandarac]

Add wonder victory timeout, last man standing option, fix a TODO, rename ID_MapTeams to ID_MapLockTeams.

[Sandarac]

The last man standing checkbox will be disabled and set to false if lock teams is set to true, like in gamesetup.js. The wonder victory timeout option will be disabled when a non-wonder victory condition is selected (it might be nice to use a slider for the timeout option).

[elexis]

About the feature:

• I'd be happy about numerical input elements like for starting resources (there is also a ticket for numerical inputs for resources and wonder victory time in the gamesetup, #4381). bb suggested to use a slider. It's just my personal opinion, so I might be wrong.
• L149 could use a range loop, see wiki:Coding_Conventions#Misc
• (Merge conflicts with the atlas 2 UI ticket / github rewrite (#3414). It is heavily outdated, but if updated and rebased, your patch will be rewritten in some way.)
• Keeping the rfc keyword as the patch looks like it works and improves the code. (Didn't run it though).
• Sentences start with a capital letter.

About the tests:

• Don't like duplicate json files. A similar discussion occured in #2951.

In case we keep the _test copy, so that the test can be executed without a public mod, the json file could be reduced a bit, to make it more transparent that we don't require an exact copy of the original and so it's less to read (while still covering a number of values, probably even a wider range than in the original). The test json is also completely independent from the public json. Someone can completely rewrite one json format and the tests still succeed. It were useful if the tests would fail. It could try to (additionally?) load the json file from the public mod and repeat the test (there was code cited launching the public mod cited in #2951)

• Your test only checks whether some strings are included in the JSON file, bad practice. The test should verify that the JSON file is actually a valid JSON string, that the numbers occur in the right place etc.. Compare with test_json() of test_ScriptInterface.h. (Contrary to what the name suggests, ReadJSON only opens the file and parses it as UTF8 text).

• The tests are supposed to check for edge cases, so why not add 2^16. The answer would be that the test doesn't actually test anything except that a file load works. The simulation supports U32 values while atlas UI only supports i32 as far as I know, so everything above 2^16 would be lost by the GUI. Unfortunately we don't have atlas GUI tests afaik.

[Sandarac]

Fix issues pointed out by elexis, and use a numerical input element for the wonder victory timeout.

[Sandarac]

The patch has been ported to Phabricator. ​https://code.wildfiregames.com/D95