feat: Create embeddings for meeting templates

[Dschoordsch]

Description

Fixes #9772
[Please include a summary of the changes and the related issue]

Demo

[If possible, please include a screenshot or gif/video, it'll make it easier for reviewers to understand the scope of the changes and how the change is supposed to work. If you're introducing something new or changing the existing patterns, please share a Loom and explain what decisions you've made and under what circumstances]

Testing scenarios

• run the migration
• start the embedder
• wait for a bit
• see the embeddings being generated in PG

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[Dschoordsch]

This one should wait until I verified or implemented the logic to update the updatedAt timestamp of meeting templates on prompt changes.

[nickoferrall]

+1 would using kysely work here instead?

[Dschoordsch]

I think it would. I'm not sure what I would gain in that case. I guess typesafety after the up migration was run, but that seems a bit odd 🤔
Any particular reason we should use kysely in migrations?

[Dschoordsch]

I don't see any examples of this elsewhere and I have some concerns regarding the typecheck. The typecheck would fail before it was run. In theory we could end up with migrations which never pass typecheck if the types differ between up and down too much.

[nickoferrall]

I think it's easier to read with kysely. The big SQL string feels more error prone to me. There's a little bit more type safety too as it ensures you write alterTable etc correctly. But I don't think it matters much.

There is a recent migration from Matt that used kysely: https://github.com/ParabolInc/parabol/blob/0092d0baf6852e820384ae114f59e23294fed0e9/packages/server/postgres/migrations/1712075131388_retroReflectionGroups2.ts