Rudder

We want to make "rudder" repository the main, only repository needed to to build rudder "web application" (ie everything that has the same release cycle than rudder web app).

That means: all the scala sources, agent, most packaging logic, system techniques...

The target organisation of the repository will be:

rudder
|- .git
|- webapp
|   |- sources (or code?)
|   |   |- technique-editor
|   |   `- rudder-parent-pom, scala-ldap, …
|   `- package (configuration)
|       `- SOURCES content for rudder-webapp
|- agent
|   |- sources
|   `- package
|- system-techniques
|- ...

To simplify the migration process, we will start with the scala projects: they are relatively self-contains, have lower impact on third party utilities (like packaging, etc).

Of course, we want to keep history of all repositories, even if the histories are reorganized (for ex sequenced by repository).

So, this ticket is here to trace (even if there won't be PR associated) what is going on:

- move the current content of "rudder" (src, rudder-core, etc) into a new "rudder/webapp/sources/rudder"
- import rudder-parent-pom into rudder repo, in directory "rudder/webapp/source/rudder-parent-pom"
- same for other scala repos: scala-ldap, ldap-inventory, rudder-common.