Prepare for Pydantic v2 migration

[Orhideous]

See: home-assistant/core#110762
See: home-assistant/core#99218

[joostlek]

Instead of moving and removing all kinds of tests, you could add a second test step where you install the v1 version (since via the poetry.lock file it will probably install v2 for the normal test) and then test? That would validate both usages imo.

[joostlek]

So now my big question is, why do we need to move all the tests in this PR?

But I am no maintainer, just something that I am remarking

[Orhideous]

@joostlek The thing is I actually added a unit-test for this, but messed with naming, so it wasn't even detected. If you prefer, I can split PR :)

[joostlek]

I personally think, this PR should just contain the changes for this change, and nothing more. (But again, I'm not a maintainer so I don't do the calls here :) )

[Orhideous]

You're right. I have moved irrelevant changesets to a separate branch — there is actually much more work to do with tests.

[pschmitt]

I don't see the benefit in testing against pydantic v1 in roombapy, this is temporary at best.

Home Assistant is stuck on v1 for now but that does not warrant roombapy running the tests on v1 as well imo, I'm fine with just yoloing the tests on v2 and live with the deprecation warnings for now.

As a the sole maintainer (hehe, plz send help) I'd rather just see the pyproject.toml changes and pydantic v1 compat usage changes in this PR.

[Orhideous]

@pschmitt

I would like to help maintain this integration, just to keep the home herd of Roomba rolling.

As for testing... I can keep an eye on home-assistant/core#99218, so when HA migrates from Pydantic v1, I just drop these workarounds and tests.

[pschmitt]

@Orhideous you asked for it :)

[pschmitt]

Thanks ❤️

[pschmitt]

Imma craft a release for ha