[Feature Request]: Add 'url' field to citations constructed during sayCommand function execution

Scenario

When I use azure_search data source which adds citations to the bot's response in Teams, the added citations do not come with links to the sources. When the citation objects are initially returned by gpt-4o, they do include a url field, but that field is not carried over to the bot's response that is constructed in the sayCommand function (as seen in actions/SayCommand.js, lines 32-41). For this reason, the user cannot go back to the sources that the bot bases its answer on, and the bot therefore cannot double as a smart search engine. This is a pity because it otherwise has the capacity for it.

Solution

The solution would be to add the url field to the clientCitation object construction in lib/actions/SayCommand.js, lines 32-41, i.e. turn block A into block B:

Block A

const clientCitation = {
    '@type': 'Claim',
    position: `${i + 1}`,
    appearance: {
        '@type': 'DigitalDocument',
        name: citation.title || `Document #${i + 1}`,
        abstract: Utilities_1.Utilities.snippet(citation.content, 500)
    }
};

Block B

const clientCitation = {
    '@type': 'Claim',
    position: `${i + 1}`,
    appearance: {
        '@type': 'DigitalDocument',
        name: citation.title || `Document #${i + 1}`,
        abstract: Utilities_1.Utilities.snippet(citation.content, 500),
        url: citation.url
    }
};

I made the change temporarily on my local machine to see what would happen, and surprisingly, I did not even need to make changes to the bot's code to fetch the urls from the citations and add them to the message, the urls appeared in the bot's messages by themselves, once the url field was added to the clientCitation objects in the sayCommand function, as seen in Image A which is taken prior to adding the url field and Image B which is taken after:

Image A: Without url

Image B: With url

I haven't found the block of code in the library that is responsible for making the links appear in the bot's message autmatically.

Additional Context

No response

Start in lib/actions/SayCommand.js at the clientCitation construction around lines 32-41 and trace how citation fields are carried into the bot response. Preserve the source URL in the citation output, then verify that Azure Search citations expose their links in Teams messages.