feat(federation): Federated table sharing

[benjaminfrueh]

Federated table sharing

Allows sharing tables with users on other Nextcloud instances.

Todo

• Schema, outgoing share and frontend support
• Incoming share: create local table on receiving instance
• Read support: fetch columns and rows from owner instance
• Write support: create, update and delete rows on remote table
• Permission propagation
• Delete local table on receiving instance when table or share is deleted on owner instance
• Update table metadata (title, emoji) when updated on owner instance
• Update view metadata (title, emoji) when updated on owner instance
• View federation
• Admin config to enable/disable tables federation
• Unit and E2E tests

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not needed
• 🔙 Backport requests are created or not needed: /backport to stableX.X
• 📅 Milestone is set
• 🌸 PR title is meaningful (if it should be in the changelog: is it meaningful to users?)

🤖 AI (if applicable)

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

[grnd-alt]

Did not entirely check all code paths yet. But the general structure looks good 🔥

What I noticed though: when creating a federated share it instantly shows as a new table on the receiving user's view. In Deck I think we're sending a notification that the user has to confirm before it shows in the app, so user's don't get spammed.

[benjaminfrueh]

Did not entirely check all code paths yet. But the general structure looks good 🔥

What I noticed though: when creating a federated share it instantly shows as a new table on the receiving user's view. In Deck I think we're sending a notification that the user has to confirm before it shows in the app, so user's don't get spammed.

Thanks for the feedback! After checking Deck's shareReceived(), it also seems to insert the board immediately and just sends an informational notification without accept/decline flow.
An "Pending shares" acceptance flow, similar to how Files handles federated shares would maybe be a good addition to both deck and tables federated sharing - maybe we can consider it as a follow-up feature?