Task fails to refresh the JWT token with LocalExecutor

### Under which category would you file this issue? Airflow Core ### Apache Airflow version 3.2.2 ### What happened and how to reproduce it? ** Issue Description ** With the LocalExecutor having a DAG executing an task that runs e.g for 3 hours or more. In about 100 minutes, the task is killed for missing / expired heartbeat. The task itself fails to send the heartbeat because of expired JWT token. Seems that the task does not refresh the JWT token. If the EXECUTION_API__JWT_EXPIRATION_TIME is set to much longer value from the default 600s, the task will continue running. ** Steps to Reproduce: ** With similar setup as described in: https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html#concepts-task-instance-heartbeat-timeout The default configuration: AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_SEC=0 AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_TIMEOUT=300 AIRFLOW__EXECUTION_API__JWT_EXPIRATION_TIME=600 Run the DAG: dag_TEST_TIMEOUT.py: ``` from airflow.sdk import DAG, dag from airflow.providers.standard.operators.bash import BashOperator from datetime import datetime, timedelta import os name='TEST_TIMEOUT' default_args = { 'owner': 'airflow', 'depends_on_past': False, 'email_on_failure': False, 'email_on_retry': False, 'retries': 0, 'retry_delay': timedelta(minutes=5), 'type': 'utf-8' } # https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html#concepts-task-instance-heartbeat-timeout @dag(start_date=datetime(2021, 1, 1), schedule="@once", catchup=False, default_args=default_args) def sleep_dag(): t1 = BashOperator( task_id="sleep_180_minutes", bash_command=""" echo AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_SEC: $AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_SEC echo AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_TIMEOUT: $AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_TIMEOUT echo AIRFLOW__SCHEDULER__TASK_INSTANCE_HEARTBEAT_TIMEOUT_DETECTION_INTERVAL: …