clear task's next_method and next_kwargs when clear the task

[Greetlist]

clear task's next_method and next_kwargs when clear the task

closes: #19120
related: #19612

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

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[Greetlist]

It seems stuck at Tests/ Wait for CI images(pull_request), What can I do now?

[uranusjr]

Let it try again

[uranusjr]

I merged the latest upstream main to your branch so this can run against the latest CI configuration. There are some recent improvements that may help this pass CI.

[Greetlist]

There are some failing checks which caused by AssertionError.
tests/jobs/test_scheduler_job.py

TestSchedulerJob::test_max_active_runs_creation_phasing():
    """
    Test that when creating runs once max_active_runs is reached that the runs come in the right order
    without gaps
    """

    ...
    ...

    expected_execution_dates = [datetime.datetime(2016, 1, d, tzinfo=timezone.utc) for d in range(1, 6)]
    dagrun_execution_dates = [
        dr.execution_date for dr in session.query(DagRun).order_by(DagRun.execution_date).all()
    ]
    assert dagrun_execution_dates == expected_execution_dates   #AssertionError

I check the error info, is the dagrun_execution_dates list missing some elements?I have no idea what goes wrong here.

[kaxil]

Should we add some sort of unit test for it?

suggestions @uranusjr @dstandish ?

[uranusjr]

Some additional asserts in TestClearTasks should be good enough.

[dstandish]

The description says this closes #19120 but that issue is already closed.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[Greetlist]

Can I reopen this PR or start a new PR for it ?

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.