Begin next development cycle

…erviceclient-does-not-use-configured-java-trust-store-for-https

Use existing tls and authentication configuration for FlareWebserviceClient

…ent-does-not-support-flare-base-url-with-path-segment

Respect Path of Flare Base URL

BPE validates the version number and rejects any version not conforming
to the X.X.X.X format.

…e-url-is-not-checked-for-null-or-empty

Check for Empty Flare Base Url and Catch Invalid URI Errors

readlink -f doesn't work on Mac and we don't really need it.

Before changing something at the CQL Process Steps, first a refactoring
of the tests.

…atic-connection-test-to-flare-or-fhir-store-at-startup

Check Connection to Store or Flare on Startup

Going back to using Camunda multi instance subprocess for sending and
receiving single dic tasks. This process flow avoids optimistic lock
exceptions.

Make it more obvious which step in the camunda process caused an error
by having the node id's, which are shown in error messages, named
equivalent to the display name in camunda modeler.

…uest-process

Refactor request process to utilize process parallization of the camunda process engine