feat: add support for multimodal indexing

[kyteinsky]

No description provided.

[marcelklehr]

So, after the update, the admin has to run this command to queue multimodal files?

[kyteinsky]

yep, but only for the existing files, the new files and updated files would be auto queued, if the corresponding task types are present.

[marcelklehr]

Would it be expected that all admins want this? Then, we could make it a migration, perhaps

[kyteinsky]

hmm, yeah it would make sense to do that since we already do all the files and would be doing all the newly detected multimodal files too.
maybe it would become necessary to also implement this then: #195

[kyteinsky]

since the ignore path is not there yet and probably won't be in the next release, it would be better to not queue all the images and audio for indexing automatically but only the new ones IMO since there might be a lot of them and with the command there would still be a choice.
wdyt?

[marcelklehr]

I think it's a weird mechanism. Either the admin wants all multimodal files indexed or none. If the issue is that the a migration would just add all files without asking the admin, we should have multimodal indexing off by default. And have a switch in the context chat settings that turns it on for all files.

[kyteinsky]

yeah that works too, setting and a command to do that.

[marcelklehr]

Please no command

[kyteinsky]

why not? It would just be a caller of a service like the UI.

[marcelklehr]

Ah, I thought you meant, admins would have to enable the setting and call the command. If it's an or then I'm ok with it :)