Disbale failing intergration test for now

Design fixes for updates

Apply password policy on user creation

Move Share backends to PSR-4 instead of using class path (#24941)

I have not been able to reproduce this failure locally yet.
But it seems to happen often on CI.
So disable for now.

Order alphabetically and deduplicate the shipped.json

Correct name in Console Application.php

Fix file permissions for SMB (read-only folders will be writeable) (#…

see changes :)

Fix #724 by using step instead of job

[master] Add new apps as official

Exit from upgrade without reporting error

Add access control and automated tagging as shipped

As reported at https://help.nextcloud.com/t/silent-mode-for-occ-upgrade/2120 we should exit with a return value of 0 (zero) if the current instance is already up to date so that automatic deployment tools don't recognize that as an error.

Add more checks

Group shares with same source and target 

Add workflowengine to check-code call

In some situations, a group share is created before a user share, and
the recipient renamed the received share before the latter is created.
In this situation, the "file_target" was already modified and the second
created share must align to the already renamed share.

To achieve this, the MountProvider now groups only by "item_source"
value and sorts by share time. This makes it so that the least recent
share is selected as super-share and its "file_target" value is then
adjusted in all grouped shares.

This fixes the issue where this situation would have different
"file_target" values resulting in two shared folders appearing instead
of one.

The repair step was a bit overeager to skip repairing so it missed the
case where a group share exists without subshares but with an
additional direct user share.

Fixes #24575

Note that this is a very limited solution and eventually we want smarter
merging!