[Improve] Microsoft Teams setup flow (port of OpenRoomote #550)

[mrubens]

What changed

Port of https://github.com/RooCodeInc/OpenRoomote/pull/550 with follow-up review fixes:

• add a downloadable, generated Microsoft Teams app package to setup and settings
• simplify Teams setup around a single Entra app whose credentials also power the bot
• refactor provider setup UI so Microsoft can own its multi-step instructions
• reorder Teams setup so app values and package upload happen before bot capability configuration
• keep original Teams image attachments when a later footer-bearing reply clears the previous footer
• remove a stray incomplete Tailwind class from provider setup URL styling

Why this change was made

The Teams setup port makes self-hosted Microsoft Teams configuration easier and more reliable. Review found that moving outbound Teams images from markdown into Bot Framework attachments meant re-editing an earlier footer-bearing reply would drop those attachments, and a leftover partial text- class needed cleanup.

Impact

Operators get a clearer single-app Teams setup path with a generated app package. Teams thread replies that include image artifacts keep those images when Roomote relocates the managed footer to a newer reply.

Port notes

• The squash-merge commit from OpenRoomote applied cleanly via cherry-pick across the original files, including the new teams-app-icon-outline.png asset.
• providerSetupCopy.test.ts was renamed to providerSetupCopy.client.test.ts, matching this repo's client-test convention.
• .agent-guidance/features/web-dashboard.md auto-merged so this repo's xAI provider mention (from [Feat] Add xAI as an inference provider and Grok 4.5 to recommended models #11) is preserved alongside the new Teams paragraph; the ADO PAT copy from [Improve] Bring the Azure DevOps source-control settings section to parity #9 is also untouched.

[roomote-roomote-v1]

Re-reviewed the latest fix commit. Both earlier findings are resolved and I found no new code issues. See task

• Teams replies with images can lose those images when a later footer-bearing reply clears the footer — apps/api/src/handlers/mcp/communication-thread-replies.ts:144. Fixed: footer images now flow through ThreadReplyFooterRecord.images, clearPreviousFooter re-sends previousFooterRecord.images, and TeamsCommunicationProvider.updateMessage → updateActivity re-attaches them as Bot Framework attachments (packages/communication/src/teams-provider.ts:211, packages/communication/src/teams-bot-framework-client.ts:325). Covered by new tests across the API handler, provider, and footer-state layers.
• Incomplete Tailwind class text- — apps/web/src/app/(onboarding)/setup/ProviderSetupInstructions.tsx:48. Fixed: the stray text- was removed, leaving font-mono text-xs text-foreground truncate.

[github-actions]

Thank you for your contribution! Before we can merge this pull request, we need you to sign our Contributor License Agreement. You can sign it by posting the comment below.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (mrubens)[https://github.com/mrubens]
❌ @brunobergher
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[mrubens]

@openmote can you fix the issues?

[roomote-roomote-v1]

I'm on it. I started a dedicated PR follow-up task for this request, and I'll keep updates here. See task

[roomote-roomote-v1]

Fixed both review findings in 7ed3bf8. See task

• Teams footer clear now re-attaches the original Bot Framework image attachments instead of sending a text-only rewrite
• Removed the incomplete text- Tailwind class in provider setup instructions

Commit: 7ed3bf8
Revert