MINIFICPP-2624 Modularized behave tests part 1

[martinzink]

The docker tests are a great way to do integration testing but it became a bit clunky over the years.
I've recreated the framework with simplicity in mind. Its now be able to create a flow (without concrete processor classes) and do simple checking with them. Any domain specific checking or containers should be moved into the respective extension.

This will enable us to use the framework to test separetly built extensions in the future (upcoming stable c api).
And hopefully this will make writing of these tests to be a bit more straight forward.

---

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced
  in the commit message?

• Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

• Has your PR been rebased against the latest commit within the target branch (typically main)?

• Is your initial contribution a single, squashed commit?

For code changes:

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE file?
• If applicable, have you updated the NOTICE file?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.