refactor: extract Jakarta EE to separate module

[ronjaquensel]

Splits the code into different modules to allow using other controller/web technologies (like e.g. Spring). The code is split into the following modules:

• core: contains dataplane, logic interfaces, stores and model classes
• web-jakarta-ee: contains the existing controllers (based on Jakarta EE API)
• e2e-tests: contains all tests using the API

In a subsequent PR, the Postgres stores could also be extracted to a separate module.

Additional notes

• method for extracting the control plane id from the auth header has been moved from the controller to the Dataplane class, as this holds the Authorizations anyway and thus makes the logic available for other controller implementations
• the methods returning the controllers have been removed from the Dataplane class, as they were only used in tests and coupled the dataplane to the specific controller implementation. Controllers are now instantiated separately

Closes #53

[ndr-brt]

as for now, this package will be published with this groupId/artifactId:
org.eclipse.dataplane-core:core, maybe it would be better to call it sdk or dataplane-sdk to make it org.eclipse.dataplane-core:dataplane-sdk, as there could be something more in the future (see in the "rust" world there are also "facet" and "siglet")

we could keep a convention like:

• org.eclipse.dataplane-core:dataplane-sdk
• org.eclipse.dataplane-core:dataplane-sdk-jakarta-ee

and so on

[ronjaquensel]

good catch! I'm so used to it from EDC that I completely missed that 😄 adjusted it. I opted for dataplane-sdk-core instead of just dataplane-sdk, as with just the core module it would be missing the controllers and dataplane-sdk could sound like it's complete

[ndr-brt]

this module should be excluded from the publication