Don't re-patch pods that are already controlled by current worker (#26778)
Don't re-patch pods that are already controlled by current worker (#26778)

After the scheduler has launched many pods, it keeps trying to
re-adopt them by patching every pod. Each patch-operation
involves a remote API-call which can be be very slow.
In the meantime the scheduler can not do anything else.

By ignoring the pods that already have the expected label,
the list query-result will be shorter and the number of
patch-queries much less.

We had an unlucky moment in our environment, where each
patch-operation started taking 100ms each, with 200 pods in
flight it accumulates into 20 seconds of blocked scheduler.
apache/airflow,nathanielvarona/airflow,apache/airflow,nathanielvarona/airflow,nathanielvarona/airflow,nathanielvarona/airflow,apache/airflow,nathanielvarona/airflow,apache/airflow,nathanielvarona/airflow,apache/airflow,apache/airflow