change multi module setup to support extension and examples

[jangalinski]

following a pattern that we used for many extensions in the past (see https://github.com/camunda-community-hub/camunda-rest-client-spring-boot for example) I would like to restructure the layout so we have

• root
  • examples
    • example 1
    • example n
  • extension
    • core
    • spring
      • spring
      • spring-boot
    • ...

This has proven to be a very effective multi module layout that allows to have multiple examples within the same mono-repo that are not published to maven central.
Not using sub folders easily leads to a cluttered repo when the number of examples and extensions increases.

[berndruecker]

Hey @jangalinski -I am not against this, but also don't think it adds much value at the current stage, so I personally would probably invest energies in other areas. But hey - if this feels important to you I suggest that you simply go ahead :-)

The beauty of that change would be, that you could drag the example from https://github.com/camunda-consulting/code/tree/master/one-time-examples/camel-use-cases into the repo itself - I definitely like this part :-)

[jangalinski]

yeah, you are right ... this can wait