Investigate custom target classes

As noticed in 2d625f0 - many overrides of `canTarget()` ought to be reviewed and cleaned if possible
- Use an ObjectSourcePlayer predicate and standard filter logic instead of custom target class, if no dependence on other targets
- Maybe can create some shared logic for effects where one target depends on another target (e.g. shared type, same controller, lesser mana value, etc.)
- If `canTarget()` override is needed, generally must also override `possibleTargets()`

Start by locating the card classes that override canTarget() and checking their possibleTargets() implementations. Compare each override with ObjectSourcePlayer predicates and standard filter logic, including effects with dependencies between targets. Done means unnecessary custom target classes are cleaned up, shared logic is identified where appropriate, and required possibleTargets() overrides remain consistent.

Written by the indexing model from the issue text.