kie-issues#966: Move the BPMN Quarkus Dev UI package from kogito-apps to kie-tools

[pefernan]

Closes apache/incubator-kie-issues#966

This PR brings the jbpm-quarkus-devui maven modules from kogito-apps into kie-tools. It includes the following changes:

• Added the @kie-tools/maven-base package to be used as a parent for all the maven-based packages in kie-tools.
• Fixed impersonation issues in TaskForm component that was affecting the jbpm-quarkus-devui.

[tiagobento]

Instead of hard coding the dependencies version here, I think we should be reusing the values from env. There's other packages doing this.. See https://github.com/apache/incubator-kie-tools/blob/main/packages/dev-deployment-kogito-quarkus-blank-app/install.js

[tiagobento]

@pefernan I see there are changes done to runtime-tools-process-dev-ui-webapp and runtime-tools-process-webapp-components that seem unrelated... do you mind adding a comment about them to the PR description?

[tiagobento]

@pefernan I just remembered something. For Maven packages to successfully be installed and not require the -D properties we require during the build, we need to run a Maven plugin called flatten-maven-plugin. The configuration is standard, and I think you can just configure it at the maven-base package, in the <build><plugins>. Every Maven package on kie-tools need to run it so that the published pom.xml doesn't depend on the build properties we pass.

[pefernan]

@pefernan I just remembered something. For Maven packages to successfully be installed and not require the -D properties we require during the build, we need to run a Maven plugin called flatten-maven-plugin. The configuration is standard, and I think you can just configure it at the maven-base package, in the <build><plugins>. Every Maven package on kie-tools need to run it so that the published pom.xml doesn't depend on the build properties we pass.

right!