Fix XCom PATCH/POST to store native values (instead of json.dumps)

[henry3260]

Why

The public Core API's create_xcom_entry and update_xcom_entry previously used json.dumps(patch_body.value) when storing values in the XComModel.value JSON column. This caused "excessively serialized" values (strings or None) when tasks called xcom_pull(include_prior_dates=True) to retrieve XComs from past DagRuns.

closes: #59032

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

• Yes (please specify the tool below)

---

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

[bugraoz93]

Look good to me! .set() already always does delete and insert. It ensures the object in the model is rendered from .set(). This should resolve it.

@amoghrajesh, could you please also check?

[jason810496]

Look good to me! .set() already always does delete and insert. It ensures the object in the model is rendered from .set(). This should resolve it.

Yeah, LGTM as well. Thanks for the fix!

[amoghrajesh]

I tested this, just one query, but looks good otherwise

[amoghrajesh]

Why this change?

[henry3260]

Why this change?

Hi @amoghrajesh, I updated this to align with the modern SQLAlchemy 2.0 syntax. While .filter() still works here, .where() is the canonical method when using select() constructs.
Let me know if you'd prefer I revert this part.