Microsoft 365 connector: add Teams meeting AI recap (aiInsights) — meeting notes are unreachable by any path

### Problem Statement

Teams meetings produce a Copilot recap — notes, decisions and action items — but the Microsoft 365 connector cannot read it. There is no recap tool; the Copilot notes file is a `.loop`, which `read_resource` rejects because `.loop` reports `application/octet-stream` and that type is not on the connector's allowlist; and no recap is delivered by email.

The only meeting content the connector can reach is the raw transcript, which is a different artifact than a recap: much larger, unstructured, carrying ASR errors, and — on recurring meetings — resolving to the wrong occurrence (#206). Reconstructing a recap from a transcript is both lossy and expensive.

Net effect: **there is currently no way to obtain a meeting summary through the connector.** For any workflow that tracks decisions and commitments across many meetings, this is the largest single gap in the connector's coverage of Teams.

### Proposed Solution

Add read support for the Meeting AI Insights API, which Microsoft exposes in Graph **v1.0**:

```
GET /copilot/users/{userId}/onlineMeetings/getAllAiInsights
GET /copilot/users/{userId}/onlineMeetings/{onlineMeetingId}/aiInsights
GET /copilot/users/{userId}/onlineMeetings/{onlineMeetingId}/aiInsights/{aiInsightId}
```

with the delegated scope **`OnlineMeetingAiInsight.Read.All`**.

`getAllAiInsights` is the one that matters most — it enumerates insights across all meetings a user took part in, which is the shape a periodic "what happened this week" pass needs. Per-meeting lookup alone would still require enumerating meetings first.

The payload is already structured, so it needs no interpretation on the way in: `meetingNotes` (title, summary, subpoints), `actionItems` (description plus assigned owner), `viewpoint.mentionEvents` (mentions with timestamps).

**Constraints worth knowing for scoping:** requires a Microsoft 365 Copilot license; the API does not support channel meetings; insights can take up to 4 hours after the call to appear; the meeting must have had transcription or recording enabled; and it covers only meetings that have not expired under Teams retention.

### Alternatives Considered

_No response_

### Area

MCP Connector (adding/managing servers)

### Priority

High - Major improvement needed

### Additional Context

_No response_