[MarioPym]

Summary

SharesPlugin builds the oc:share-types property with array_unique(), which keeps the original keys. When a node has more than one share of the same type (e.g. two user shares and a link), ShareTypeList::getShareTypes() returns [0 => 0, 2 => 3] instead of [0, 3].

The XML output is the same, because the serializer only iterates the values. But the property is not a list anymore: any code that reads getShareTypes() and encodes it as JSON gets an object ({"0":0,"2":3}) instead of an array ([0,3]).

This wraps the result in array_values() and documents ShareTypeList as list<int>, so psalm can catch it in the future.

How to test

1. Share a folder with two users and create a public link for it.
2. Check getShareTypes() of the oc:share-types property for that folder (the XML response does not show the keys):
   • Before: [0 => 0, 2 => 3] (as JSON: {"0":0,"2":3}).
   • After: [0, 3] (as JSON: [0,3]).
   • The XML response (<oc:share-types>) does not change.

Unit test: testGetPropertiesReturnsListWithRepeatedShareTypes in apps/dav/tests/unit/Connector/Sabre/SharesPluginTest.php. The existing data provider never repeats a share type, so this case was not covered.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI