enh(integrity): do not expect ocm-provider anymore

[blizzz]

The ocm-provider dir was removed in 26.0.8 and 27.1.2.

[blizzz]

test needs updates… the stable ones fail of course.

[blizzz]

I removed now all non-master tests…

[come-nc]

Why are you removing all tests?

[blizzz]

Why are you removing all tests?

I am removing tests against NC 24 to 26, because they are failing due to presence of the ocm-provider file (https://github.com/nextcloud/updater/actions/runs/6417991835/job/17424862460, https://github.com/nextcloud/updater/actions/runs/6417991840/job/17424861208).

This updater branch runs in reality on 28 only, therefore the tests against the old versions were already suspicious and may give you a wrong picture of both expectations and results.

[come-nc]

Why are you removing all tests?

I am removing tests against NC 24 to 26, because they are failing due to presence of the ocm-provider file (https://github.com/nextcloud/updater/actions/runs/6417991835/job/17424862460, https://github.com/nextcloud/updater/actions/runs/6417991840/job/17424861208).

This updater branch runs in reality on 28 only, therefore the tests against the old versions were already suspicious and may give you a wrong picture of both expectations and results.

But these tests are testing the updater in several scenarios, such as beta versions, minor versions, wrong signature, and so on and so on.
You can read the feature files to get the list: https://github.com/nextcloud/updater/tree/master/tests/features

If you merge this the only test remaining is updating from master branch to master branch which only happens on developer setups and none of the productions scenarios are tested anymore.