Possible bugs with effects applying to phased out permanents

As noticed in https://github.com/magefree/mage/commit/5c9d1cd205fd8df1c38d4b21c0edbba474de52d6#r140928934 , phasing logic may not be checked everywhere it needs to be.

A few reported bugs over the years: https://github.com/magefree/mage/issues?q=is%3Aissue+%28phasing+OR+phased%29 and some associated fixes that check `isPhasedIn()` for a particular effect. It ought to be getting handled deeper in the engine. There are also a few checks to `isPhasedOutIndirectly()` which I think are superfluous as that should only be for internal use.

Example: #8213 was fixed with the following:
https://github.com/magefree/mage/blob/f75b1c9f0aa8f17c6df4e2570c39739a9a2691b7/Mage/src/main/java/mage/abilities/effects/common/ReturnToHandSourceEffect.java#L73-L77

But there are many other effects that could change zone. So if it is needed it should be deeper, perhaps all the way down in `ZonesHandler` ?

Another example: #8549 was fixed by adding a check to `ClassLevelAbility`, though I think it might be more appropriate in `PermanentImpl::setClassLevel`, similar to #9194. This is the only usage though so not as big a deal. But still, we don't want to have to check phased in status for all these methods in `Permanent`.

Next thought, for usages of `source.getSourcePermanentIfItStillExists(game)`, should this return null if phased out? After all, a phased out permanent is treated as though it doesn't exist.

And then even for `getPermanent`, are there legitimate use cases to find a phased-out permanent?

If only a few specific known cases need to find phased-out permanents, then special method could be created for those, and the general case should not find phased-out permanents. This would eliminate the need for other methods to check phased in status.

Any associated rework needs to ensure that previously solved bugs have test coverage.