Right now user has to manually add containers to Kie server router. Added container has to have same GAV, same container id and alias as the one created in Kie server. This is uncomfortable for user and error prone.

It would be good if Kie server router was able to register all needed containers to controller by itself. For this action it can use controller's REST API.

Sequence of possible actions (managed Kie server):
----- These are currently executed steps ----
1. User creates new container in Server template.
2. Controller send a request to Kie server to create new container.
3. Kie server creates new container.
4. Kie server sends a request to Router to add container.
5. Router registers a container in internal configuration
------ New steps -----
6. If container wasn't registered yet in Router's configuration then Router sends a request to Controller to register container into Router's server template
7. Controller adds container to Router's server template.

Removing of containers could work on similar principle. Whenever there are no other Kie servers containing this container, Router sens request to COntroller to remove this container from Router's server template.