Currently the vault migration is using StakeManager to call new StakeVault and set its storage.

While this works, its not ideal, because the StakeVault should be responsible for its own migration on its own (not depending on StakeManager to complete it).