Refactor Mission Control for re-use

[quintesse]

The idea is to:

1. Move the "web" part of Mission Control to the backend, which means:
   1. Move the code
   2. Integrate with the backend
   3. Update any code, configuration and OpenShift templates that expects to talk to mission control to now talk to the backend
2. Merge OSIO's "launch" code into ours in Mission Control
3. Make OSIO's addon use Mission Control

[quintesse]

Right now step 1 is being developed in the following branches: https://github.com/fabric8-launch/launchpad-backend/tree/accept-web-from-missioncontrol and https://github.com/fabric8-launch/launchpad-missioncontrol/tree/move-web-to-backend

Up to now the following steps have been performed (simplified):

• Moved everything in backend/* to a new submodule called backend/forge
• mv missioncontrol/web backend/missioncontrol
• mkdir backend/web
• mv backend/forge/src/main/webapp/WEB-INF backend/web/src/main/webapp/
• mv backend/missioncontrol/src/main/webapp/WEB-INF backend/web/src/main/webapp/
• Added a parent pom to the backend with 3 sub modules (forge, missioncontrol and web)

And finally edited all the poms to make things compile.

[gastaldi]

Merged into https://github.com/fabric8-launch/launcher-backend

[gastaldi]

These steps are still missing:

2. Merge OSIO's "launch" code into ours in Mission Control
3. Make OSIO's addon use Mission Control

[gastaldi]

Step #2 seems done. We're working on bringing the OSIO to the same repository and refactoring to consume the mission control services

[gastaldi]

Opened openshiftio/openshift.io#1499 to deal with the OSIO addon refactoring. Closing this now