Run different version of mypy in ci

[UnknownPlatypus]

I have made things!

Run ci with supported mypy version ie 1.13, 1.14, 1.15, 1.16 and master branch on github.

[UnknownPlatypus]

@sobolevn This is ready for review, was much easier now that we have uv.
I had to use type: ignore[unused-ignore] for type ignores that were required on old versions but not required in newer ones.
We should aim at removing them when we drop older mypy/python version support

[sobolevn]

I am not quite sure about that :(
It brings several new quirks for maintenance, not sure if it really helps though...

[UnknownPlatypus]

I am not quite sure about that :(
It brings several new quirks for maintenance, not sure if it really helps though...

Yeah I'm also not completely sure, but it would have caught #2665 earlier and would have probably also help with #2724 (comment) were a mypy version bump introduced a regression in our plugin.

I feel like the kind of bugs related to mypy versions are the complicated ones, often related to the plugin.

Maybe others core maintainer of django-stubs have an opinion on the subject ?

[ngnpope]

I fear this is about to become even more non-viable. In mypy 1.17 or 1.18 various options related to the formatting of types in errors are going to be obsolete. This means that we'll need to fix our tests - I have a branch ready with some of those changes which I'll open a PR for when the next release comes along... But, yeah, testing across versions will be nigh on impossible.

[UnknownPlatypus]

That's sad but yeah, I suppose it would add too much of a burden