Airflow CLI client based on Stable API

**tl;dr;**: [Hyperone](https://www.hyperone.com/) and good citizen @ad-m will be happy to help build a new Airflliw CLI. Here is docs for POC: https://gist.github.com/ad-m/19cc06d91a7ee756f461c95f5d656eb6 If we have a [Stable API](https://airflow.readthedocs.io/en/latest/stable-rest-api-ref.html) ready, we can start working on tools that use it. A highly anticipated feature is the ability to manage Airflow from the CLI. Currently, there is [similar feature](https://airflow.readthedocs.io/en/latest/usage-cli.html#set-up-connection-to-a-remote-airflow-instance) in Airflow, but with many limitations: - A very small number of commands are available (7 pool commands and 2 dag commands only). - Use deprecated experimental REST API. - Low test coverage. - No access control. (Big security risks) - Requires full Airflow to be installed along with a large number of unnecessary dependencies. - [compatibility issues on Windows](https://github.com/apache/airflow/issues/10388). - Installation is via pip which is great. However, users expect such a tool to be available as a single package with all dependencies included. I also suggested that this be deleted in Airflow 2.0 as it is rarely used. https://lists.apache.org/thread.html/rfada8ac2fce87c0516d62923e35e3bebfc44ee5a379103b890f8c61c%40%3Cdev.airflow.apache.org%3E Some users use the normal CLI, but this also has many of the disadvantages mentioned above, but for this it poses an even greater security risk as it requires a direct connection to the database. On the other hand, it has many more features, but not all that are available in Web UI, eg there is no access to remote logs but they are available in Web UI and stable API. I spoke with good citizen @ad-m how [HyperOne](https://www.hyperone.com/) will develop CLI for its services. HyperOne is a cloud provider that develops services for polish good citizens in Poland. They use OpenAPI very intensively for build thier platform. They also strive for automation and self-mainte…