Migration from oasp4j to devon4j

[hohwille]

We want to migrate OASP entirely into Devon in the future. This will mean:

• [x] change all groupIds from io.oasp.* to com.devonfw.*. in all pom.xml files
• [x] change all artifactIds from oasp4j-* to devon4j-* in all pom.xml files
• [x] change in packages the root package io.oasp to com.devonfw.
• [x] align BOM groupIds - see #653
• [x] push all into https://github.com/devonfw/devon4j as a huge initial commit (see https://github.com/devonfw/devon4j/pull/1).

With this big shift a lot of things change and therefore we break compatibility. We will address this with https://github.com/devonfw/devcon/issues/135. However, this gives us also the opportunity to do some historic cleanups:

• 653 align all BOMs to common groupId

• 611 resturcture layout - we can revisit and cleanup things here if we want

• decouple more and get rid of mmm dependencies (at least all except mmm-core). This was desired from Spain but never brought to action. Maybe a good point to revisit...

[hohwille]

https://github.com/devonfw/devon4j/pull/1/files

[hohwille]

@AbhayChandel did all this. I have merged his PR so all is done and in place: https://github.com/devonfw/devon4j For the last polishing already separate issues have been created. Hence this one is considered done.