feat: multiple phone number for profile

[mykh-hailo]

• Resolves: Allow to add multiple phone numbers to the profile #38607

Summary

This change adds support for multiple phone numbers on user accounts, following the same model as additional email addresses.

Previously, personal settings only exposed a single primary phone number via AccountPropertySection. Users can now manage a primary phone number plus additional numbers, including federation scope per entry, from Settings → Personal info.

Backend

• Introduce IAccountManager::COLLECTION_PHONE (additional_phone) as a new account property collection (since 33.0.0).
• Extend the Provisioning API (UsersController) to add, update, remove, and scope additional phone numbers, with the same permission checks used for additional emails.
• Expose additional_phone and additional_phoneScope in OCS user data responses (AUserDataOCSController).
• Sanitize additional phone numbers in AccountManager using the existing E.164 validation path.
• Include additional phone numbers when exporting CardDAV vCards (Converter).
• Update OpenAPI definitions for the new fields.

Frontend(settings app)

• Replace the single-field PhoneSection.vue with a dedicated PhoneSection/ component structure:
  • PhoneSection.vue — section layout, validation, and primary/additional phone coordination
  • PhoneSectionEntry.vue — individual phone input with federation controls and actions
  • PhoneService.js — OCS API client for primary and additional phone operations
• Extend AccountPropertyConstants with PHONE_COLLECTION, readable labels, supported scopes, and DEFAULT_ADDITIONAL_PHONE_SCOPE.
• Provide phoneMap (primary + additional phones) via initial state in PersonalInfo.php instead of a single phone property.

Behavior

• Additional phone numbers are validated client-side (libphonenumber-js) and server-side (existing phone sanitization).
• Duplicate numbers (including matching the primary phone) are rejected by the API.
• Updating phone numbers clears known-user contact matches, consistent with primary phone changes.

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