I recently had some trouble trying to fix a bug in the CeleryExecutor <https://github.com/apache/airflow/pull/14883>. The code change was small, but it was really difficult to set up a development environment using the CeleryExecutor. I ultimately had to muck around with the test case that covers this situation, default_airflow.cfg, and default_celery.py. Developing using Docker <https://airflow.apache.org/docs/apache-airflow/stable/start/docker.html> would require an update to the image each time you want to make a change to the codebase (or maybe `exec`ing into the relevant container?) which is a pain.
This led me to two questions: 1. Would it make sense to allow developers to choose the executor for their Breeze environment? 2. If not, how do folks test out changes they make to the CeleryExecutor or KubernetesExecutor? Thanks! Ryan
