fix(dav): Use an exhaustive list for allowed serialized classes

[come-nc]

Summary

This is simpler and clearer than trying to guess namespace.

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)

[AndyScherzinger]

🐘

[come-nc]

/backport to stable33

[come-nc]

/backport to stable32

[solracsf]

/backport to stable33

[come-nc]

/backport to stable33

[come-nc]

/backport to stable32

[backportbot]

The backport to stable32 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable32
git pull origin stable32

# Create the new backport branch
git checkout -b backport/58095/stable32

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 669ff56f

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/58095/stable32

Error: Failed to push branch backport/58095/stable32: remote: Invalid username or token. Password authentication is not supported for Git operations.
fatal: Authentication failed for 'https://github.com/nextcloud/server.git/'

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.