KIE WB to kie-server capability check fails.

When KIE WB embedded kie-server controller tries to connect to the kie-server a "capabilities" check is produced that introduces an issue.

This are the steps to reproduce.

1) use last build from master
2) start a jbpm-server-distribution or a business-central distribution
3) when KIE WB is starting and tries to connect to the kie-server the following error is show:

14:39:31,237 WARN [org.kie.server.controller.impl.KieServerControllerImpl] (default task-8) Server id sample-server capabilities expected [KieServer, BRM, BPM, CaseMgmt, BPM-UI, BRP, DMN, Swagger, Prometheus] but there was [PROCESS, RULE, PLANNING]
14:39:31,237 WARN [org.kie.server.controller.rest.RestKieServerControllerImpl] (default task-8) Server with id 'sample-server' failed to connect

4) BUT even when the displayed log entry is a WARNING, the issue really causes that the embeded KieServerController in KIE WB can't connect to the kie-server.

After debugging I believe it's related with the capability codes used by KIE WB and the capability codes used by kie-wb

It looks like KIE WB uses PROCESS, RULE and PLANNING while kie-server uses BRM, BPM, BRM etc.

Below goes a couple of pointers to the code I've could see:

Here's where check is performed:

https://github.com/kiegroup/droolsjbpm-integration/blob/4d182fd6dc286f5e1b33a00a1f1c0bfaea757a02/kie-server-parent/kie-server-controller/kie-server-controller-impl/src/main/java/org/kie/server/controller/impl/KieServerControllerImpl.java#L226

Note that here a kie-server error messages is added

serverSetup.getMessages().add(new Message(Severity.ERROR, "Expected capabilities were " + serverTemplate.getCapabilities()));

And this line makes the connection fail

https://github.com/kiegroup/droolsjbpm-integration/blob/4d182fd6dc286f5e1b33a00a1f1c0bfaea757a02/kie-server-parent/kie-server-controller/kie-server-controller-rest/src/main/java/org/kie/server/controller/rest/RestKieServerControllerImpl.java#L79

since an error was stored in the serverSetup.

I'd suggest taking a look carefully especially because if a previous versions of KIE WB / business central are storing this capability code in any kind of storage and the tries to connect to a newer kie-server version the check will fail.