Detect docker flavor

[ckunki]

Fixes #301

All Submissions:

• [x] Is the title of the Pull Request correct?
• [x] Is the title of the corresponding issue correct?
• [x] Have you updated the changelog?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change? yes, there are other PRs.
• [x] Are you mentioning the issue which this PullRequest fixes ("Fixes...")
• [ ] Before you merge don't forget to run all tests for all Exasol version, by adding [run all tests] to the commit message
• [x] Are the CLI usage examples up to date?

Not yet, I leave this as a question for the review of the PR:

• The current PR is part of a set of tickets covering all steps of the overall roadmap epic.
• The feature "SSH access" will be available to end users only after all tickets have been implemented.
• Updating the user guide (incl. examples) is currently planned as a separate step.

Should we update the user guide and examples already in the scope of the current ticket? Should we use a feature branch and only merge it to main branch after all related tickets are implemented?

[tkilias]

And the test failures in CI probably indicate, that you pass a string into the EnumParameter instead of the Enum-Value.

[ckunki]

I have the assumption that the failure of job Test Docker Starter / test-docker-starter could have been caused by the new version 1.5.0 of poetry.