Improve Pydantic v1/2 cross-compatibility

[hrshdhgd]

Update @validator decorator to @field_validator since the former will be deprecated/removed in future versions.

Warning that triggered this PR:

python3.10/site-packages/curies/api.py:253
../site-packages/curies/api.py:253: PydanticDeprecatedSince20: Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.5/migration/
    @validator("prefix_synonyms")  # type:ignore

Solution:
~@validator~ => @field_validator

[hrshdhgd]

This may be a crude solution to comply with Pydantic 1.x. I'll leave it upto you @cthoyt, to disregard PR or merge it.

[cthoyt]

@hrshdhgd do you know if there's a pydantic compatibility layer package (like six for the python 2->3 transition)? There are so many people that would benefit from not having to re-think this over and over again

[hrshdhgd]

I think as per pydantic docs, there is bump-pydantic

[hrshdhgd]

I ran bump-pydantic src/curies and this is what I got: https://github.com/hrshdhgd/curies/pull/1/files#diff-155777c613bd355b6a0a9df37a38484289b2f70f971bf6353cb1560ac1415a6b

I also undid everything from this PR and ran bump-pydantic. Instead of refactoring the code to be Pydantic 2 compliant, it just adds a TODOs. e.g.:

# TODO[pydantic]: We couldn't refactor the 'validator', please replace it by 'field_validator' manually.
# Check https://docs.pydantic.dev/dev-v2/migration/#changes-to-validators for more information.

[codecov]

Welcome to Codecov 🎉

Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.

Thanks for integrating Codecov - We've got you covered ☂️

[cthoyt]

@hrshdhgd that wasn't what I was thinking - rather, I was wondering if there was re-usable code that wraps the logic for writing cross-compatible pydantic models, not if there was code for upgrading

i found https://github.com/pyapp-kit/pydantic-compat btw, seems a bit heavy so for now I think we can just keep a small compatibility layer internal in curies