feat(microsoft): emulate Teams discovery and bot messaging

[kamal]

Review and landing order

Independent PR targeting main; no stack dependency on the other emulator addition. Ready for code review based on the package-level validation below. GitHub currently reports no PR checks, so this is local-validation evidence rather than a green hosted CI claim. Review and merge either addition first; recheck shared documentation/lockfile overlap on the second PR.

Snapshot: 2026-09-06. Recheck checks and approvals after rebasing or retargeting.

Summary

Teams bot messaging requires Graph discovery and Bot Framework Connector delivery. Add Graph user, installed-app and chat discovery alongside authenticated Connector conversation creation, send, reply, update and delete. Preserve rich card payloads and expose an emulator-only read-back endpoint backed by the shared store.

Add seed configuration for conversations and installations, tenant-qualified token endpoints, bot access checks, and meaningful input/resource/authentication failures. Update package and root documentation, agent instructions, docs site and CLI help.

Validation

• 37 Microsoft tests pass, including 8 new Teams tests.
• Official Bot Framework Connector SDK covers create, send, reply, update, delete and error decoding through an in-process HTTP transport.
• Wire tests cover discovery-to-card delivery, authentication failures, malformed input, bot isolation, stateful read-back, conversation recovery, snapshots and reset.
• Type-check, core and Microsoft builds, and built-artifact token/send/read-back smoke pass.
• Lint has zero errors and two pre-existing warnings in unchanged Microsoft files. Changed CLI files pass ESLint; formatting and whitespace checks pass.

Limitations

No inbound bot events, card callbacks, incoming webhooks, Graph message writes, installation writes, pagination or throttling. Cards are retained as JSON with basic validation. Full tenant/consent simulation and external SDK token discovery are not covered; seed OAuth clients for credential validation. No live provider or deployed environment validation was performed.