fix(settings): confirm app-token revoke and preserve wipe state

[pringelmann]

Summary

Revoking an app password now opens an NcDialog confirmation. For tokens marked for remote wipe the dialog uses a red error card and the destructive button reads "Revoke and cancel wipe", so cancelling an in-flight wipe is a deliberate click rather than a side effect of clicking the trash icon.

Two admin-only deletion paths used to drop the wipe marker the same way the user-facing controller did. Both are guarded now: occ user:auth-tokens:delete refuses wipe-pending tokens unless --cancel-wipe is passed, and OAuth2 client revocation skips matching wipe-pending tokens (with a log line) so the wipe outlives the client.

Backports needed for stable34, stable33, stable32.

Screenshot

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)

[susnux]

functionality wise approved, some code comments

[pringelmann]

/backport to stable34

[pringelmann]

/backport to stable33

[pringelmann]

/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/60644/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 05a188e3 16ca990b 4b1c3fbe eaf565f2 1d035b4c bbdb7d01 407d4fee

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

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

---

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

[backportbot]

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

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

# Create the new backport branch
git checkout -b backport/60644/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 05a188e3 16ca990b 4b1c3fbe eaf565f2 1d035b4c bbdb7d01 407d4fee

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

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

---

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