[Improve] Clarify integration tool approval prompts

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Replaces raw integration and tool identifiers in the approval prompt with a human-readable request, using catalog display names when available and a conservative generic fallback for arbitrary tools.
• Moves raw integration names, tool names, and redacted argument JSON behind an accessible Details disclosure, including the clearer empty state "No additional details."
• Clarifies the action hierarchy: Allow once is primary, Allow for this session is secondary, and Deny is a quiet ghost action.
• Uses an intentional mobile layout with full-width stacked allow actions and a compact Deny action instead of wrapped controls.

Why this change was made

The approval card exposed internal runtime vocabulary and made three choices compete visually. This keeps the decision understandable at a glance while preserving technical details for people who want to inspect the exact request.

Impact

Only the pending integration-tool approval card changes. Its transcript placement, requester-only checks, session-scoped permission behavior, and decision payloads remain unchanged.

Screenshots

Desktop

Mobile

[roomote-community]

No code issues found. See task

_{Reviewed 133ae75}