Move all UI packages from kogito-apps to kie-tools

[tiagobento]

For historical reasons that are not relevant anymore, many components that compose Runtime Tools and Quarkus Dev UI pages lived in kogito-apps. Given the reusability necessity we have amongst our many distribution channels and systems, kogito-apps ended up having a dependency with kie-tools, resulting in a circular dependency, since kie-tools depends on the JIT Executor and other artifacts hosted at kogito-{apps, runtimes}.

To solve this cyclic dependency, all packages that are currently hosted at kogito-apps/ui-packages will move to kie-tools/packages. During this migration, it is expected that the package structure will change to conform with what was already migrated to kie-tools as part of apache/incubator-kie-tools#1982.

Since many packages present on ui-packages are used by Quarkus Dev UIs that are still hosted on kogito-apps, such Quarkus Dev UI modules will move to kie-tools as well.

Things to keep in mind:

• Quarkus Dev UI modules need to be published to Maven Central on releases, so the release scripts will need to be altered. Separate issue created: Adapt kie-tools Jenkins staging/release jobs to build and deploy Quarkus Dev UI modules to Nexus/Maven Central #964
• There are images for the Task and Management consoles. Separate issue created: Move task-console and management-console images from kogito-images to kie-tools #963
  • https://github.com/apache/incubator-kie-kogito-images/blob/main/kogito-task-console-image.yaml
  • https://github.com/apache/incubator-kie-kogito-images/blob/main/kogito-management-console-image.yaml
• runtime-tools-webapp-components needs to be renamed to runtime-tools-swf-webapp-components
• runtime-tools-gateway-api needs to be renamed to runtime-tools-swf-gatewat-api
• If runtime-tools-* packages have a dependency with any backend hosted at kogito-apps, runtime-tools-* packages should consume some schema file (e.g., Open API) to be able to type its API clients.