Bump pylint, pydantic, remove "artifacts.yaml" logic

[aguschin]

👀

This will require Studio BE update - we need to remove old logic that works with artifacts.yaml - that will make Studio MR backend codebase more easy to work with! To clarify, before we already removed "write" access to old artifacts.yaml, but kept "read" access. Now we remove "read" access as well. (Please notice, that will lead to some users losing info about model versions that are 3+ months old, but I hope that's ok).

So once this merged, consider bumping major or minor version, but not the patch.

[codecov-commenter]

Codecov Report

Patch coverage is 96.87% of modified lines.

Files Changed	Coverage
gto/api.py	ø
gto/cli.py	0.00%
gto/utils.py	ø
gto/config.py	96.66%
gto/__init__.py	100.00%
gto/base.py	100.00%
gto/git_utils.py	100.00%
gto/registry.py	100.00%
gto/tag.py	100.00%

📢 Thoughts on this report? Let us know!.

[aguschin]

cc @amritghimire about changes required in BE ^

[aguschin]

@pmrowla, I assume this is what you meant to make it compatible with py-template. There are few things still that should be fixed - like remove top-level silence statements here https://github.com/iterative/gto/blob/bumping-versions/gto/config.py#L1, but overall it should be ready for py-template I hope!

[aguschin]

closes #400

[shcheklein]

Since studio depends for now on MLEM and MLEM depends on the first Pydantic, will those co-exist fine together or does it means we need to upgrade / drop MLEM dependency?

[skshetry]

We discussed this in today's team meeting and decided not to merge this PR due to the breakages involved. We don't want to risk merging this for now.

Most of the pylint/mypy changes has been cherry-picked into the main branch, and CI is now running from Python 3.8 - 3.11 versions now.

I have created #413 that supports both Pydantic v1 and v2, so there's no immediate need to migrate to use pydantic v2 APIs too.

(For future reference, afddc5e is the last commit before it was rebased).