chore: bump Nextcloud to 35.0.0; 34.0.4:4 → 35.0.0:0

[helix-nine]

⚠️ Needs a close review — startos/actions/maintenance/disableUnstableApps.ts; confirm Nextcloud 35's new sharing core app must remain enabled during recovery.
🧪 Needs live testing — upgrade an existing Nextcloud 34.0.4 install with user data, shares and custom apps; watch the schema migration and confirm the web UI, data and integrations survive.

Summary

• Update the official Nextcloud Apache image from 34.0.4 to 35.0.0 (major tier).
• Keep Nextcloud 35's new sharing core app out of the Disable Non-default Apps recovery action.
• Refresh the FileBrowser and NextExplorer next-branch lock pins.
• Publish the package as 35.0.0:0 with localized release notes covering the major release and its upgrade constraints.

Major-version audit

• The exact 35.0.0-apache image is published for both amd64 and arm64. It remains on PHP 8.5, and Nextcloud 35 continues to support PostgreSQL 17.
• Nextcloud 35 accepts upgrades from 34.0. The existing pre-init guard continues to reject older installations that would skip a major.
• The 34 and 35 Apache entrypoints are byte-identical: mounted paths, version-file locations, upgrade behavior and all three progress markers are unchanged.
• Every modeled config.php key remains supported or is unchanged from 34; the 35 sample removes no key this package models. The package's occ command names, options and parsed JSON fields remain available.
• Web readiness still uses port 80, install readiness still receives installed: true, and the Postgres and Valkey checks retain their existing contracts.
• Nextcloud's own occ upgrade handles the new schema migrations during the snapshotted init path, so no StartOS data migration is needed.
• @start9labs/start-sdk is already current at 2.0.9, and the dependency refresh retains one SDK copy.

Testing

After rebasing onto the current master, npm ci, npm run check, tsc --noEmit --noUnusedLocals, npm run build, Prettier, and full x86_64/aarch64 package builds passed. The runtime upgrade remains to be tested.

• Upgrade an existing 34.0.4:4 install with user files, shares and custom apps to 35.0.0:0; confirm the copying and database-migration phases complete, the Web Interface check becomes healthy, and files, shares and compatible apps remain available.
• Run Configure, restart the service and confirm the selected locale, phone region, maintenance window, trash retention and skeleton-files choice persist.
• Enable a non-default app, run Disable Non-default Apps, and confirm that app is disabled while the built-in sharing app remains enabled and the web interface still loads.
• On an install with external storage and an office or Talk integration already configured, restart after the upgrade and confirm the mount, connector health and relay settings still work.

Merge with a merge commit — do not squash. next is long-lived: a merge commit leaves it a true ancestor of master, so it fast-forwards cleanly afterwards. A squash re-lands the same content under a new commit, so the branch is left carrying history master will never contain.