SerDe: Check more strictly for pydantic model

[Desdroid]

Ensure that pydantic dataclasses are not detected as pydantic models.

As discussed in #56739 check more strictly for pydantic models and avoid detecting pydantic dataclasses as pydantic models.
Went with the suggestion of @amoghrajesh and used stdlib dataclasses to check that the detected model is not a dataclass.

Fixes: #56739

---

^ 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 airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[sjyangkevin]

@Desdroid thanks for the PR. The change looks good to me.

While testing the change; I noticed to deserialize this pydantic dataclass, we do need to whitelist it, I hope it is something we also need to do before. The current implementation ensure to deserialize only known objects, due to security considerations.

To whitelist it, we can configure the following airflow config, below is an example.

[Desdroid]

I am not sure I understand you.
This PR does not change the need to whitelist custom classes that one wants to serialize / deserialize.
One still needs to add them or the package to the whitelist - that's also what we do in our setup.
Do I also need to change stuff in the default breeze setup?

[Desdroid]

@sjyangkevin So can you tell me what else is required? CI test are good.

[sjyangkevin]

@sjyangkevin So can you tell me what else is required? CI test are good.

It looks good to me. Would be great to have a second eyes on it @amoghrajesh , @bolkedebruin

[amoghrajesh]

Thanks for your contribution @Desdroid!
Some nits, otherwise looks good.

[amoghrajesh]

Just rebased it to fix the CI

[amoghrajesh]

@uranusjr can you take another look at this one?

[Desdroid]

@bolkedebruin Alright, moved it back up then.

[amoghrajesh]

LGTM, @bolkedebruin / @uranusjr?

[amoghrajesh]

Manual backport: http://github.com/apache/airflow/pull/57616