chore: use more detailed AI Summary for meetings

[nickoferrall]

Fix #10049

This PR updates the way we generate AI Summaries in meetings to use the more the detailed approach used in generate insights.

Now, when ending a retro meeting, we'll generate the AI Summary by using the same logic that dumps the data to a yaml file.

We're also using the updated prompt which encourages the use of links.

To test

• End a retro meeting and see that the AI Summary looks good
• Generate retro summaries for a team and see it works well with generateRetroSummaries

[nickoferrall]

This code comes from the previous generateMeetingSummary file

[Dschoordsch]

+1 I think the name is misleading. I would assume this function does just generate a summary for a meeting and returns it. Instead it updates the table.
I would prefer if we'd change it to updateRetroSummary and also remove the return type, so it's less likely to be used wrongly.

[nickoferrall]

I feel like updateRetroSummary suggests it already exists and we're updating it, but we're creating a new summary here.

Maybe addRetroSummary instead of generateRetroSummary? I like that generate describes that this is where it's being created.