Add `execute_tasks_new_python_interpreter` argument to `PythonOperator`

### Description

Currently from my knowledge it is only possible to force all python tasks to execute in a new
interpreter for every execution globally via this setting:

- https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#execute-tasks-new-python-interpreter

Would it be possible to add this argument to the `PythonOperator` so it is possible to control this behavior at the task level?

### Use case/motivation

- https://github.com/apache/airflow/discussions/40956

### Related issues

- https://github.com/apache/airflow/discussions/40956

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

Start with the PythonOperator and the existing execute-tasks-new-python-interpreter configuration described in the linked configuration reference. Review the related discussion for the task-level use case. Done means the operator can control whether its Python task runs in a new interpreter, independently of the global setting.

Written by the indexing model from the issue text.