[#38284] Update Confirmation Logic for Config Changes on Sensitive Environments Like Production

[maycuatroi]

Description

I've added a configuration option require_confirmation_dag_change to both the config.yml and the Flask App. Its default value is False. However, when a user sets this configuration to True, the Dag screen (Dag.html) will enforce a logic that requires users to confirm before they can Trigger a DAG or Pause/UnPause a Dag.

This feature is particularly effective for teams working across multiple environments, including sensitive ones like Production.
Note: The confirmation is similar to the confirmation box displayed when deleting a Dag.

Related issue:

• Resolve: Dag trigger confirmation popup for Production Environment #38284

Test Screen

---

^ 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: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[hussein-awala]

It looks good.
Here is the static checks doc you need to fix the failed tests.

[maycuatroi]

@hussein-awala I've fixed the static check issue. Thank you for your advice.

[maycuatroi]

@potiuk sorry for taking your time. I'm fixed the ruff check. Please approve trigger the workflow to run test. 🙆‍♂️

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[hussein-awala]

Congrats on your first commit 🎉