Rename fail stop dag property to fail fast

[hprassad]

closes: #45229
This PR renames fail_stop DAG property to fail_fast, the changes made to relevant files

---

^ 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

[amoghrajesh]

@hprassad FYI, I updated your PR description to link the issue.

[Lee-W]

Overall, I'm good with this PR, but we'll need a newsfragment for it

[amoghrajesh]

There are a couple of occurences which have been missed in tests.
Ref:

Also, needs a newsfragment addition. Example: https://github.com/apache/airflow/pull/43902/files#diff-802ca1cc091ad2e4489cfdb8cb02678d0bc42db3a6b9081859a2ee66b415b94e

[amoghrajesh]

@Lee-W do we have to add this one into migration rules too?

[Lee-W]

@Lee-W do we have to add this one into migration rules too?

Yes, this can be easily detected. I’ll create a PR for this later

[potiuk]

@hprassad - I rebased it -> we found and issue with @jscheffl with the new caching scheme - fixed in #45347 that would run "main" version of the tests.

[Lee-W]

I think we'll need newsfragment for this one

https://github.com/apache/airflow/blob/main/contributing-docs/16_contribution_workflow.rst#step-4-prepare-pr

[amoghrajesh]

Yeah the changes look good @hprassad. Can you please add newsfragment as mentioned by @Lee-W?

[hprassad]

@amoghrajesh & @Lee-W , I have added file in newsfragments folder for the PR