Ability::getTargets() wrongly used in some use cases (unsupport multi-modes spells/cards)

`Ability::getTargets()` do not work with multi modes abilities and return only first mode's targets (it's about ability's targets, not cost's targets).


It's works fine in 95% cause most of the usages work with a single mode cards. But it will fail on usage with 2+ mode cards.

Usages examples:
1. Update dynamic targets (search by `getSpellAbility().getTargets().clear()`):
* 
2. Access to targets data like filters, selected ids, etc (search by `.getTargets().get(`):
* 
* 

Some hints on good usage:
* if you're sure there are a predefined targets then can use index/first access (current usages);
* if you work with unknown abilities/targets then use:
* List of all selected target ids: `CardUtil.getAllSelectedTargets(ability, game)`
* List of all possible target ids: `CardUtil.getAllPossibleTargets(ability, game)`
* List of all target classes (if you need filters, canTarget, etc): `Ability::getAllSelectedTargets()`

What can be fixed/refactored:
* [ ] search and fix of `getStackAbility().getTargets()` (some use cases must use all target ids by `CardUtil.getAllSelectedTargets(ability, game)`):
* [ ] need research and find another use cases to fix;

Start by searching for getStackAbility().getTargets() and other getTargets() usages, then compare each use with CardUtil.getAllSelectedTargets(ability, game), CardUtil.getAllPossibleTargets(ability, game), and Ability::getAllSelectedTargets(). Audit the relevant usages for multi-mode abilities and update those that need all target data; done means multi-mode spells and cards no longer lose targets while single-mode behavior remains correct.

Written by the indexing model from the issue text.