AIP-72: Handling "up_for_reschedule" task instance states

[amoghrajesh]

related: #44414

Server side changes (execution api):

1. Handling TIRescheduleStatePayload in ti_update_state -> covered by unit test: test_ti_update_state_to_reschedule
2. Defining a datamodel for TIRescheduleStatePayload and adding it to the discriminator: ti_state_discriminator

Client side changes (task sdk):

HTTP client:

Added a new function defer that sends a patch request to the task-instances/{id}/state execution api with payload: RescheduleTask

Comms:

Defining a new data model to send a request to patch ti as "up_for_reschedule" from task runner to supervisor: RescheduleTask (Added to ToSupervisor)

Supervisor:

1. Extended handle_requests to receive requests from task runner and forwarding the message to http client to call reschedule.

TaskRunner:

Task runner executes: ti.task.execute and raises AirflowRescheduleException for rescheduling. This sends a request to supervisor using SUPERVISOR_COMMS

Example DAG with which this was tested:

from datetime import datetime, timedelta
from airflow.exceptions import AirflowRescheduleException
from airflow.decorators import dag, task
from airflow.utils import timezone


@dag()
def reschedule_dag():
    @task
    def raise_reschedule_exception(**kwargs):
        raise AirflowRescheduleException(reschedule_date=timezone.datetime(2025, 1, 1))

    raise_reschedule_exception()


reschedule_dag()

---

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

[kaxil]

Approving (lgtm high-level), but please address the comments

[amoghrajesh]

@kaxil merging this one. I think I have handled the comments on this