Tests with wrong choice must be researched and fixed

There are many tests with possible wrong choices (~126 tests). It's can be by design (use case requires an invalid or empty choice) or it's can be an error (miss choice setup).

Possible fixes:
* add correct choice commands;
* add `checkPlayableAbility` command instead real cast with wrong choices;

How to find:
* in test logs by `Wrong choice`
* in source code by `//Assert.fail("Wrong choice");`

Start by reviewing test logs for “Wrong choice” and searching the source for `//Assert.fail("Wrong choice");`. For each of the roughly 126 tests, determine whether the choice is intentional or indicates missing setup, then apply the appropriate listed fix. Done means the intentional cases are documented or handled and erroneous wrong-choice failures no longer occur.

Written by the indexing model from the issue text.