Motivation / Problem

AI started from the console with an exact version behaved strangely. This is a long outstanding issue. #7193 tries to solve it, but the solution felt rather complicated. So I dived in to find the root-cause .. turns out it is a 10 year old bug :D

I wrote out my full analysis here:
#7193 (comment)

Fixes #6468

Description

Fix #6468: don't store version of AIs started via console in name

You can do: "startai myai.3", which starts version 3 of "myai".
This is very useful for testing save/load code between different
versions of your AI.

However, when using this syntax, the AI got saved as "myai.3" as
name of the AI, instead of "myai". This caused several problems,
like indicating to the user the AI could not be found, but still
load the AI. But in all cases, the AI never got the chance to
load the saved data, making the whole reason this exists pointless.

By splitting the name and version already in the console command,
the code becomes simpler and AIs started this way now follow the
normal flow after initialization.

Limitations

• Save/load loads the latest compatible AI; one could think that when started with the exact version, it should retain that. This makes no sense to me, as the only real reason I can think of that you want to load an older version, is to check if your save/load code still works. If other use-cases present themself, we can always store the force_exact_match variable next to the AI. But as I currently do not see the use-case, I left that out.
• This does not fix old savegames; in fact, one could argue it breaks old savegames more, as it doesn't even try to load the AI anymore with any version (which it did use to do, despite telling in the console it did not).