Unify how docker commands get executed in Breeze

[potiuk]

So far we executed commands in CI image in breeze in two ways:

• entering the shell (which runs docker-compose under the hood)
• running docker run with the CI image

This requires rather complex mapping of environment variables
between docker-compose and docker. Since recently (#35862)
we can use shell command to run commands in very similar way
as docker run (with docker-compose, without database and extra
components - just using the same breeze shell mechanisms.

This PR converts all the usages of docker run CI_IMAGE we had
and converts them to use modified enter_shell method that has
been moved to "docker_command_utils". This also simplified
passing arguments to the "enter_shell" command - no longer need
to filter out none parameters and **kwargs - all parameters are
passed explicitly.

This also allowed to remove some of the code (extracting args,
filtering_out_none) that are not used anymore.

The entypoint CI has been slightly refactored - to provide
a bit better structure and handle --skip-environment-initialization
better - we can now both set --use-airflow-version and
--skip-environment-initialization which was not possible
before.

---

^ 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 will not be needed anymore

[potiuk]

Right. Solved all the problems - should be ready to review now :).

This is one more cleanup (including removal of +200 lines of redundant codee) where we have an easier way to understand and add new commands for breeze in the future.