Add the ai-agent commands for the conversations the AI Sessionizer lands

[wu-sheng]

What

The OAP (apache/skywalking 11.1.0, branch feat/ai-agent-conversation, not yet merged) stores the conversations of long-lived AI agents that the AI Sessionizer pushes under the AI_AGENT layer, and serves them through two GraphQL queries and one streamed HTTP route. swctl gains a command group for them:

Command	Reads	From
ai-agent list	one row per conversation of a service, newest first, with the sender filter and --limit	GraphQL listConversations
ai-agent files	the raw files as stored; --export DIR writes each body to its id path, a storage root asz verify and asz view read	GraphQL getConversationRawFiles, body @include on export
ai-agent view	the whole conversation as one asz.view 1.0 document, JSON or --yaml, streamed to stdout or --output	GET /ai-agent/conversations/{id}/v1/view on the --base-url host

Why the view is not a GraphQL query

A long conversation renders to tens of megabytes (a 136 MB session folds to a 70 MB document), so the OAP serves it from a streamed route on the query host beside /graphql, with Content-Type: application/vnd.skywalking.asz.view+json; version=1.0 (or +yaml) and errors as application/problem+json. pkg/aiagent/view is therefore a small streaming client of its own rather than a use of the admin REST client, which is bound to the admin host and buffers bodies: it derives the host from --base-url, shares TLS and basic auth through pkg/transport, copies the body through, and turns a problem document into the error.

Other changes

• goapi is bumped to the regeneration that carries the conversation types (Add the AI agent conversation query protocol skywalking-goapi#98), and dist/LICENSE follows.
• That regeneration dropped MenuItem, because the query protocol retired getMenuItems; the menu command keeps the shape locally for backends before 11.0.0.

Dependencies

• ai-agent: add conversation query protocol for the AI Sessionizer skywalking-query-protocol#166 and Adapt the new record query API for sub-command metrics sampled-record #167 (merged): the queries and the route; Bump up text module #168 (open, comment-only): the media-type wording.
• Add the AI agent conversation query protocol skywalking-goapi#98 (merged).

Verification

• Unit tests run the view client against an in-process server: JSON and YAML bodies, streaming, the instance parameter, and the 400, 404 and 500 problem paths.
• The end-to-end check lives in the OAP repository, not here: the OAP's ai-agent e2e builds sessions with the Sessionizer, pushes them to the OAP built from that PR, and reads every conversation back through swctl ai-agent list, files and view. It passed 10/10 locally with this branch's binary; once this PR merges, the OAP e2e pins the merged commit as SW_CTL_COMMIT and runs it in CI.