feat(ContactsInteraction): Allow write-properties to support sort favorites feature

[DerDreschner]

Summary

Right now, the automatically added Recently contacted address book only allows read requests. That's insufficient for the favorite contacts feature, as we need to allow write-properties here as well. There are no additional changes necessary, as the properties are automatically being written to the oc_properties table.

Refs nextcloud/contacts#105

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

[kesselb]

Fine by me.

I would like to mention that those contacts are automatically deleted when you did not interact with them in the last 7 days¹ and hence its a bit weird to favorite them?

Footnotes

1. https://github.com/nextcloud/server/blob/d56ad83c1cad5786c098b3be0210e38b94325a2c/apps/contactsinteraction/lib/Db/RecentContactMapper.php#L106-L114 ↩

[DerDreschner]

Hmm, good point... @ChristophWurst: Should we allow that case or not? @GretaD had some code in that checked for that, but on the wrong ACL property (address book modifyable or not instead of write-properties).

[ChristophWurst]

Given how volatile the data is I wouldn't allow fav'ing or any other property.

Let's have a check for that ACL in the frontend and exclude them.

[DerDreschner]

@GretaD: Do you need any changes in the backend for that?