XD-1983 NodeExistException on ModuleMetadata write

- Ignore ZK `NodeExistsException` on writing module metadata as this
is likely to happen when the container disconnects and reconnects
but the admin leader was not available to handle the container
departure event.
  - In this case, upon container disconnect the modules on that
container get undeployed and when the container reconnects
the `DeploymentListener` makes sure to deploy the same modules
except the fact that the ZK paths for the deployment and module
metadata already exists.
In this case, the module is going to be the same that was previously deployed to this container including the metadata properties. I think it is safe to assume the metadata to be same (since the module deployments path etc., remains same) and keep all the ZK paths in sync with how they were before. What do you think?