Submitted by bin2chen, also found by aashar, ladboy233, and chaduke
Unable to switch to a new deploymentController.
The current protocol supports the replacement of the new DeploymentController, which can be switched by VaultController.setDeploymentController().
Normally, when switching, the owner of the cloneFactory/cloneRegistry/templateRegistry in the old DeploymentController should also be switched to the new DeploymentController.
DeploymentControllers nominateNewDependencyOwner() implementation is as follows:
But there is a problem here, VaultConttroler.sol does not implement the code to call old_Deployerment.
nominateNewDependencyOwner(), resulting in DeploymentController can not switch properly, nominateNewDependencyOwner()s Remarks:
Caller must be owner. (`VaultController` via `AdminProxy`)
But in fact the VaultController does not have any code to call the nominateNewDependencyOwner:
setDeploymentController() need call nominateNewDependencyOwner():
RedVeil (Popcorn) confirmed 
