enhancement(shares/jsoncs3): Shortcut migration on fresh system

[rhafer]

Avoid waiting in migrations on fresh systems. Some migrations are blocking the correct startup of the service until dependent services are up and running, we don't need this on a fresh system.

Fixes: opencloud-eu/opencloud#3392

[maki5]

some time ago I introduced this method https://github.com/rhafer/reva/blob/0d5e08ab4906528f24f2282f3a19f8d3aa258d36/pkg/share/manager/jsoncs3/jsoncs3.go#L371
for the same issue with test flakiness, but in case of the fresh system it seems to not be needed anymore with your change, can we consider using it in combination with your changes?

So basically to have it like:

• on fresh system we mark migrations as applied
• on non fresh we wait until migrations are actually applied

regarding just the introduced change LGTM

[rhafer]

some time ago I introduced this method https://github.com/rhafer/reva/blob/0d5e08ab4906528f24f2282f3a19f8d3aa258d36/pkg/share/manager/jsoncs3/jsoncs3.go#L371 for the same issue with test flakiness, but in case of the fresh system it seems to not be needed anymore with your change, can we consider using it in combination with your changes?

So basically to have it like:

* on fresh system we mark migrations as applied

* on non fresh we wait until migrations are actually applied

Hm, originally (when we implemented the first migration) the intention was to still be able to serve Read Requests (listing Share, getting an individual share), that is why we currently do not block until a migration has finished. For now, I think we can keep it that way. In the long run we might need to reconsider here.