MCP Apps: Add ergonomic WithAppTool helper to reduce wiring boilerplate

From PR #1484 review comment by @halter73:

Ergonomics suggestion (worth considering as a follow-up): the TypeScript @modelcontextprotocol/ext-apps package exposes a registerAppTool(...) helper that bundles tool registration + UI resource linkage in one call. Today a C# user has to do WithTools<T>() + WithResources<T>() + WithMcpApps() + [McpServerTool] + [McpAppUi] + a matching [McpServerResource] with the right MIME type. A combined WithAppTool(method, resourceUri, htmlFactory) overload — or at least a doc section showing the "complete recipe" end-to-end — would cut the wiring boilerplate significantly.

Consider adding a combined helper (e.g. WithAppTool) that bundles tool registration + UI resource linkage into a single call, similar to the TypeScript SDK's registerAppTool(...) pattern.

Inizia leggendo la discussione della revisione in PR #1484 e tracciando l’uso corrente di WithTools(), WithResources(), WithMcpApps(), [McpServerTool], [McpAppUi] e [McpServerResource]. Confronta il pattern TypeScript registerAppTool(...), quindi chiarisci se il risultato desiderato sia un overload C# WithAppTool o una ricetta di documentazione end-to-end. Il lavoro è completato quando l’approccio scelto rimuove o documenta chiaramente il wiring ripetuto dello strumento e della risorsa UI.