Creation of new auxiliary chains should be resumable

[schemar]

Story

As a user
I want to resume a failed creation command
Because I don't want to repeatedly pay deployment transaction fees on origin

Scenarios

Given that I run the command to create a new auxiliary chain
When the command fails
And I rerun the command for the same chain
Then it resumes after the last previously successful step

Info

This means the mosaic config of the new auxiliary chain must be written after every update to keep the data available in case of an error.

It is probably sufficient to resume execution after the last step that was successfully recorded in the mosaic config, and not track every tiny step individually. That still provides the benefit of not repeating the deployment transactions, which are probably the most expensive ones.

[benjaminbollen]

it's too complicated for now. The Night King is dead but putting it on ❄️