Expose conversation display names in resource listing APIs

[stropalov]

Name and Version

0.0.1

What is the problem this feature will solve?

Conversation resource listings currently return name derived from the resource URL, rather than the name stored inside the conversation JSON.
When Chat renames a conversation, it updates the JSON while preserving the resource URL. Consequently, resource listings still contain the original filename, and clients must fetch each conversation’s full content to retrieve its current title. This also affects conversations shared with other users.

Example

A conversation is created with the title hello and stored at:
conversations/<owner-bucket>/pg-agent__1.0.0__hello__<uuid>

The owner renames it to renamed. The conversation JSON now contains:

{
  "name": "renamed",
  "messages": ["..."]
}

However, POST /v1/ops/resource/share/list with:

{
  "resourceTypes": ["CONVERSATION"],
  "with": "me"
}

still returns:

{
  "resources": [
    {
      "name": "pg-agent__1.0.0__hello__<uuid>",
      "url": "conversations/<owner-bucket>/pg-agent__1.0.0__hello__<uuid>",
      "nodeType": "ITEM",
      "resourceType": "CONVERSATION",
      "permissions": ["READ"]
    }
  ]
}

What is the feature you are proposing to solve the problem?

Expose a separate displayName field containing the current conversation title, while preserving the existing meaning of name and keeping the resource URL unchanged:

{
  "resources": [
    {
      "name": "pg-agent__1.0.0__hello__<uuid>",
      "displayName": "renamed",
      "url": "conversations/<owner-bucket>/pg-agent__1.0.0__hello__<uuid>",
      "nodeType": "ITEM",
      "resourceType": "CONVERSATION",
      "permissions": ["READ"]
    }
  ]
}

What alternatives have you considered?

No response