[master < T] Pydantic v2

[as51340]

Description

Bumped pydantic to v2.3.0

Pull request type

Please delete options that are not relevant.

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring with functional or API changes
• Refactoring without functional or API changes
• Build or packaging related changes
• Documentation content changes
• Other (please describe):

Related issues

Delete section if this PR doesn't resolve any issues.

Closes (link to issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

######################################

Reviewer checklist (the reviewer checks this part)

• Core feature implementation
• Tests
• Code documentation
• Documentation on gqlalchemy/docs

######################################

[antepusic]

Approving this; I’ve linked this PR to the associated issue

[as51340]

@antepusic it is still not working, problems with some type

[katarinasupe]

@as51340 we should be careful with migration to Pydantic v2 and how that affects our users and us. This guide might help: https://docs.pydantic.dev/latest/migration/#migration-guide. The conclusion of this PR might also be us not moving to Pydantic v2 for now (if you conclude it's too much work for now). But, notice also what users suggested in the linked issue: #257 (comment) . I also found this in their migration guide that might help: https://docs.pydantic.dev/latest/migration/#continue-using-pydantic-v1-features

[katarinasupe]

There is also a tool that might help if we migrate: https://docs.pydantic.dev/latest/migration/#code-transformation-tool