Update rector to 2.0

[come-nc]

Fix #34

Not sure about all the changes, I had to pull OCP so that rector finds the classes.
I had to delete my composer.lock and start from scratch, and I set platform php to 8.1 to avoid composer pulling a psalm too recent (otherwise it only runs on latest PHP).

[come-nc]

The lowest tests fails because I did not set a minimum version for nextcloud/ocp I suppose. Maybe we can set that to 25 as that’s the oldest set we have?

[come-nc]

The lowest tests fails because I did not set a minimum version for nextcloud/ocp I suppose. Maybe we can set that to 25 as that’s the oldest set we have?

I had to require 27 so that tests on 26 and 27 sets pass.

[provokateurin]

So it has to be the highest supported version so all changes can be made?

[come-nc]

So it has to be the highest supported version so all changes can be made?

Yeah, seems like it.
In applications it may be annoying, because you usually require nextcloud/ocp for the lowest supported version, not the highest.
Solutions:

1. Version this library in sync with nextcloud/ocp, release a version for each NC major
2. Change the tests to require the nextcloud/ocp of a version before running the associated set test suite

For now maybe we can merge as-is, as 27 is not that recent and should be ok as a requirement for apps using nextcloud/rector?

But yeah later when we populate sets for 31+ it’s gonna be a problem, so maybe we tackle it now 🤷

[provokateurin]

Sounds good to me, although we can and should prevent the ocp version conflict in apps by putting rector into vendor-bin.

[provokateurin]

New release? @ChristophWurst