[ISSUE-21603] Reenabled passing cmd configuration

[2ps]

Problem?

Not including _cmd configuration options broke configuration for
sql_alchemy_conn_cmd and fernet_key_cmd which caused all tasks to
fail with a mysterious sqlite error.

Solution!

Reenabled including _cmd configuration values when creating the
temporary configuration used to run tasks.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[ashb]

Please tell us how to reproduce this when it currently causing a problem.

[potiuk]

Yep. Agree with @ashb - we need to know what problems you had how you diagnozed that this was it and how the change is fixing it.

[ashb]

Closing in favour of 21539

[2ps]

@ashb -- jsut as an FYI--we referenced an issue that we opened that would describe the problem that we were creating. In the future, would you like us to include the issue description in both the PR and the issue, or just the issue?

[ashb]

I didn't notice at first the issue number in the title as GitHub didn't link it for me.

If you are also going to open a PR, you can skip the issue and directly describe the problem in the PR