feat(match): fly the behaviour the scenario asked for master
A V2 scenario can give each faction its own `bot:` block, and MatchHost was throwing it away: every Princess was constructed on the default profile whatever the file said. lance.blue's Bug Company asks all three pirate lances for Striker - aggression 9, self-preservation 2, herd 7 - and the card on the front page says so, so the match was advertising behaviour it did not run. The lookup has one trap in it. Bot behaviour is keyed by the scenario's own slot name, and the rename above replaces that with the display name the manifest wants shown - so asking for the behaviour of "@lance.blue" finds nothing. The slot each player came from is now remembered as it is renamed, and the lookup goes through that. A V1 scenario carries no such block and keeps the default, which is what it did before.