feat(principal): map CalDAV room metadata properties

[Rikdekker]

Summary

Extend the principal model in src/models/principal.js to extract room-specific properties from CalDAV principal responses. These properties are defined in the CalDAV standard and already served by Nextcloud room backends, but are not yet used by the Calendar frontend.

Mapping them into the principal model makes them available for any future UI improvement (such as the room finder in the follow-up PR) without changing how principals are fetched.

What

Adds 7 new properties to the principal object (defaults null for non-room principals):

Property	DAV source	Notes
roomSeatingCapacity	roomSeatingCapacity	Number or string
roomType	roomType	Trimmed
roomFeatures	roomFeatures	Trimmed; comma-separated list
roomBuildingAddress	roomBuildingAddress	Stripped of leading/trailing whitespace and commas
roomBuildingName	Derived from roomBuildingAddress (first segment before comma)
roomNumber	roomBuildingRoomNumber	Trimmed
roomAddress	Constructed from above	Used for event LOCATION field

The string sanitization (leading comma strip, trim) handles edge cases like CSV-imported room data with empty building-name fields, e.g. , Science Park 140, 1098 XG, Amsterdam → Science Park 140, 1098 XG, Amsterdam.

Why

This change is part of splitting #7996 into focused, reviewable PRs as suggested by @nimishavijay. The principal mapping has no UI impact and is fully backward compatible (defaults null), so it can be reviewed and merged independently of the visual room finder that depends on it.

Scope

• ~50 lines added to src/models/principal.js
• Backward compatible: all new properties default to null
• No template, style, or service changes
• No new dependencies
• No breaking changes to existing principal consumers

Tests

• tests/javascript/unit/models/principal.test.js — 10 tests pass, including a new test verifying that roomBuildingAddress is correctly stripped of leading commas/whitespace.

Related

• Replaces (in part) feat(resources): Visual room browser with building grouping and filters #7996 per scope feedback from @nimishavijay
• A follow-up PR will add the visual room finder UI that consumes these properties

Test plan

• Existing principals (users, groups, circles, resources, regular rooms without metadata) still map correctly with null for room properties
• A room principal with all DAV properties set produces the expected roomBuildingName, roomAddress, etc.
• A room principal with leading comma in roomBuildingAddress is sanitized
• npm run test:unit passes

[codecov]

Codecov Report

❌ Patch coverage is 80.95238% with 4 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/models/principal.js	80.95%	3 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[SebastianKrupinski]

Hi @Rikdekker

Thank you for the PR. I will review it as soon as I can.

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)