fix(core): resolve some edge cases with recommended apps

[susnux]

Summary

There are some edge cases to keep in mind:

1. Not always install the code server if office is not installed
2. Handle installed apps properly
3. Properly handle aborted password confirmation

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

[pringelmann]

setup.ts has been failing on master since #61575. The "Install recommended apps" cases still stub the old endpoints so the intercepts no longer match.

Could be folded in here since you already touch this flow. Happy to pick it up if you're busy, just let me know.

[pringelmann]

@susnux The per-app enable loop here reintroduces multiple password prompts. #60068 switched install to a single bulk enable specifically so strict confirmation only prompts once. Installing N recommended apps now pops N password dialogs.

That's also why the setup.ts Cypress spec is red: it expects one bulk enable + one dialog.

How do you want to handle it?

[susnux]

How do you want to handle it?

Sounds like we should bring that back, but that needs backend changes now.
Lets do that in a follow up.

But the cypress test I can adjust here for now.

[joshtrichards]

Related bug: #32310