fix(maintenance): allow AppAPI to serve requests during maintenance mode

[oleksandr-nc]

Summary

This PR allows AppAPI to work during the maintenance mode.

Reason? When admin enables maintenance mode, Nextcloud returns a 503 for every app route. This also shuts down AppAPI's own routes and its occ commands. But maintenance mode is when admins run backups and upgrades, so today this can break the whole ExApp setup.

Main findings from bug-reports:

• HaRP can no longer read ExApp metadata from the NC or check user access from Nextcloud, so calls to running ExApps start failing with misleading 401/404 errors. If HaRP restarts during the maintenance window, every ExApp route stops working.
• ExApps cannot report their status back to Nextcloud (those callbacks go over OCS), so any ExApp install or update that was in progress when maintenance started is left broken.
• The occ app_api:* commands are not loaded during maintenance, so an admin cannot manage or recover ExApps from the command line either.

Conditions:

1. AppAPI must be enabled to serve it's endpoints.
2. No upgrade may be pending (needUpgrade() must be false) - as there can be a pending upgrade of AppAPI.

Everything else stays exactly as before (I hope 🤗)

We would also like to request a backport this for Nextcloud 34, for which we are already asking admins to use HaRP - and with it, this problem looks more serious.

Note: WebDAV and the other entry points are untouched. ExApp-provided dynamic occ commands (loaded from register_command.php) are intentionally not registered during maintenance.

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

[marcelklehr]

Makes sense. Changes look good. Did not test.

[AndyScherzinger]

/backport to stable34

[backportbot]

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

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

# Create the new backport branch
git checkout -b backport/61294/stable34

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

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

Error: Failed to check for changes with origin/stable34: No changes found in backport branch

---

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