Some coordinators are set up by taking an FCV region before they are spawned in getOrCreateInstance() (example).
This guarantee might also be useful for other cases that currently don't facilitate this behaviour (e.g. drop).
Moreover, sometimes a fixedFCVRegion might already be active in the scope where getOrCreateInstace() is called.
We should provide a solution that unifies those scenarios ensuring the getOrCreateInstace() always operates within a FixedFCVRegion.