Documenting effect if task state store cleanup for KPO

[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Similar to #70721 but for KPO. KPO is separately handled because it doesn't use ResumableJobMixin but directly uses task_state_store.

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[github-actions]

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker c86ba34 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

Going to move this to the 3.4.0 milestone instead of backporting it to v3-3-test.

The new paragraph appends into the "Durable execution" section of the KubernetesPodOperator docs, and that section isn't present on v3-3-test at all — the durable= parameter on KPO only exists on main, not in the 3.3.x provider. So there is nothing for this caveat to attach to on the release branch (which is also why the cherry-pick conflicts).