naming conventions proposal

[matus-m]

hi,

we are proposing an updated naming conventions for devonfw-microservices. The motivation and goals:

• Reflect the typical usage of microservices - single component, single business domain,
• Easier to navigate and immediately start working
• Persuade detractors who object that Devon4j is a bit too complex and promotes legacy package structure
• Promote simplicity and only introduce abstraction when needed
• Attempt to reduce number of abbreviations and acronyms used
• Provide guide for fixed REST API versioning

All is of course subject to discussion e.g. we could adopt dataaccess instead of domain if you think its more fitting.. we have no fixed opinion on DTO suffix... etc

Looking forward to any feedback

[CLAassistant]

All committers have signed the CLA.