Redundant methods in Player class

* `choose(Outcome outcome, Cards cards, TargetCard target, Ability source, Game game)`
* `chooseTarget(Outcome outcome, Cards cards, TargetCard target, Ability source, Game game)`

These methods are extremely similar as implemented in `HumanPlayer`. I can't find any documentation on why one would be used over the other. Perhaps they should be merged into a single method?

Start by comparing choose and chooseTarget in HumanPlayer, then search for all call sites and overrides of both Player methods. Determine whether their behavior or contracts differ; done means either consolidating them without changing callers or documenting the distinction clearly.

Written by the indexing model from the issue text.