ChainedActions spec shouldn't let certain steps to be deliberately skipped just because of availability. Either all steps should be done or none (fail).

Or deprecate ChainedAction

• and supersede with MGNLUI-5949
• use custom actions wherever ChainedAction was used internally

Someone can already be using it in a way that it skips instead of breaks (we could introduce breakage in minor)

Will need more discussions

consider if we want to have actions composable, or rather consider them atomic and use custom actions for anything more complex