XD-2026 Tweaks for storing admin metadata into zookeeper

https://jira.spring.io/browse/XD-2026

- New RuntimeRepository for admin metadata
- Following same concepts used in ContainerRepository
- Store real bind port from tomcat into this repository. RuntimeAttributes
  based on ContainerAttributes except group info has been removed.
- Metadata updates happen in DeploymentSupervisor where update logic
  is based on concepts from ContainerRegistrar.
- ZK path /xd/admins is moved over to /xd/adminelection and /xd/admins
  is now solely used for metadata in a same way that /xd/containers.
- ZooKeeperRuntimeRepository doesn't use caching because we don't
  expect a lot of runtime admin containers and we don't read that often.
Would you like to have any special handling of exceptions? Meaning ok to fail leadership if registration fails? I made it this way because felt that leadership handling is more important than registration.

I was kinda disappointed to find out that curator doesn't allow you to associate data(well it has that name/id which you cannot modify) with its leader nodes(s). Now we need to do two separate operations(election,registration).