Integration tests are separated into separate command and CI job

[potiuk]

Integration tests so far were a separate test type among the
unit tests, however we have to start them differently.

This PR introduces new command in Breeze:

breeze testing integration-tests

The --integration option has been removed from the regular
unit tests, and now it is used to the integration-tests command.

The integration-tests command has no parallel option.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

This one is based on #28209 (so #28209 should be merged first) - and it should deal with the memory issues we had in public runners (it should also speed up our tests):

1. Unit tests now do not have "Integration" as test type - so regular "matrix" tests do not run integration tests. Much less memory used for those jobs in general.

2. We have a new command in breeze breeze testing integration-tests that allows to run integration tests very easyily - for example breeze testing integration-tests --integration mongo will run mongo db tests, breeze testing integration-tests --integration all will run all integration tests

3. I have removed the old openldap integration (it turned out it is not used any more)

4. We are using the breeze command in CI in a separate job to run integration tests

5. In Self-hosted runners we run all integration tests for Postgres at once with all integrations enabled (because memory!)

6. In Self-hosted runners we also additionaly run all tests for MySQL

7. In Public runners we run the integration tests sequentially (cassandra, mongo, pinot, celery, (trino + kerberos) and we run breeze stop between each integration test type - this way we only run one/two docker-compose integrations at a time and we stop/reclaim memory after each integration test type

[potiuk]

[potiuk]

[uranusjr]

Makes sense. (I kind of not like the verbosity of breeze testing integration-tests --integration ... but I guess that can work.

[potiuk]

Makes sense. (I kind of not like the verbosity of breeze testing integration-tests --integration ... but I guess that can work.

That was the most coherent one witht the rest of the system: --integration is also used in regular shell command - if you want to enter breeze and start selected integration with it.