Decouple volume_configurations from capacity_provider_strategy

[pyrr]

closes: #43046

---

^ 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.

[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 Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, 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.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  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

[eladkal]

@pyrr can you rebase and resolve conflicts?
Also please add unit test to avoid regression

[pyrr]

@eladkal done.

[romsharon98]

@eladkal done.

Static checks need to be fixed

[pyrr]

Static checks need to be fixed

@romsharon98 Fixed extra parameter issue-- should work now but I'm not sure how to run the unit tests on my end without waiting for you to trigger the workflow.

[romsharon98]

Static checks need to be fixed

@romsharon98 Fixed extra parameter issue-- should work now but I'm not sure how to run the unit tests on my end without waiting for you to trigger the workflow.

You can read more about how to run tests locally here

[pyrr]

Static checks need to be fixed

@romsharon98 Fixed extra parameter issue-- should work now but I'm not sure how to run the unit tests on my end without waiting for you to trigger the workflow.

You can read more about how to run tests locally here

Thanks, will fix new error and QA tests on my side this time before requesting review.

[pyrr]

@romsharon98

Tested locally + squashed the bug fix commits into one, good to retry workflow.

[pyrr]

@o-nikolas

Thanks for re-running the workflow, I see the tests are still failing. Not sure why since it works when I run the suite using breeze on my machine. Will investigate again.

[eladkal]

@o-nikolas

Thanks for re-running the workflow, I see the tests are still failing. Not sure why since it works when I run the suite using breeze on my machine. Will investigate again.

It fails on static checks. You just need to install and enable pre commit. It will automaticly fix it

[pyrr]

Thanks @eladkal , I applied the pre-commit changes and fixed an additional issue with the expected_args.

Also @potiuk @ashb apologies for the code review request-- I committed another file I had modified locally for local testing.