feat: Add support for Mistral API models

[Olyxz16]

Describe your changes

Added models mistral-tiny, mistral-small and mistral-medium from Mistral API.

Issue ticket number and link

Fixes #1991

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests. - N/A
• I have added thorough documentation for my code.
• I have tagged PR with relevant project labels. I acknowledge that a PR without labels may be dismissed.
• If this PR addresses a bug, I have provided both a screenshot/video of the original bug and the working solution. - N/A

Demo

Notes

Mistral API : https://docs.mistral.ai/api/

[manyoso]

@cebtenzzre look good now?

[Olyxz16]

should be good, please review

[manyoso]

This has conflicts and needs that need to be resolved and then we'll review again.

[manyoso]

In general, I'm really happy to have someone working on updating these remote Models and consolidating the code for them / keeping them up2date as the remote API's change. Would be cool to have Claude support as well!

[Olyxz16]

it's merged !
I don't have access to claude's api, if it's similar to chatgpt's, give me the endpoint and I can add it

[Olyxz16]

In general, I'm really happy to have someone working on updating these remote Models and consolidating the code for them / keeping them up2date as the remote API's change. Would be cool to have Claude support as well!

I plan on changing the way we handle them and use the same system as the other models

[manyoso]

We have to figure out the naming convention we want and then change accordingly, but otherwise I'm happy with this. How about you @cebtenzzre ?

[Olyxz16]

So what should I do next ?
If you want to implement a prefix for the file names and get the previous names back, we will have to implement something to store the name of the api model name.

[manyoso]

So what should I do next ? If you want to implement a prefix for the file names and get the previous names back, we will have to implement something to store the name of the api model name.

Going to have @cebtenzzre look at this tomorrow but after we come up with a solution for the prefix file names and we figure out the issues below, then we're hopefully merging this week

[manyoso]

NOTE: This very closely related PR that I'm closing due to conflicts... but putting it here for posterity: #1692

[Olyxz16]

I do agree with @cebtenzzre about the naming convention of the remote model files. But the issue remains : where do we first store the name of the remote model, since it's different from the display name and the filename ?
I think we should store the remote models the same way we do with other models instead of hardcoding them, but again that would mean setting the model name somewhere into that.

[Olyxz16]

I fixed the backward compatibility issue by checking for remaining .txt file when loading the models. I then transform them into the new .rmodel format. The process then continues like before

[cebtenzzre]

@Olyxz16 Heh sorry, manyoso suggested that I make the style changes for you but apparently you were already working on it, so we duplicated some work. Looks like it came out OK in the merge.

[Olyxz16]

@Olyxz16 Heh sorry, manyoso suggested that I make the style changes for you but apparently you were already working on it, so we duplicated some work. Looks like it came out OK in the merge.

Yeah I saw your commit after my changes, no worries you changed more things than I did anyway

[manyoso]

looks like all we're missing is another conflict resolution and then this is ready to merge?

[Olyxz16]

Just merged, there was conflicts on the backend I didn't know how to solve, so I just chose the branch responsible for the changes

[cebtenzzre]

Hold on, the merge isn't quite right.

[cebtenzzre]

Fixed.

[manyoso]

Fixed.

I'm still seeing, "This branch cannot be rebased due to conflicts"

[cebtenzzre]

This branch cannot be rebased due to conflicts

Probably because rebasing merges isn't trivial. I just squashed it to keep things clean - one can click the PR link to see the history of this specific change.

[manyoso]

[manyoso]

we need a check for the prefix of the old "chatgpt-" when converting the .rmodel and probably 'nomic-' too?

[cebtenzzre]

we need a check for the prefix of the old "chatgpt-" when converting the .rmodel and probably 'nomic-' too?

It looks like Nomic Embed is not even converted and still uses the old name.

[manyoso]

we need a check for the prefix of the old "chatgpt-" when converting the .rmodel and probably 'nomic-' too?

It looks like Nomic Embed is not even converted and still uses the old name.

See #2119

I'm leaving the nomic one now as I think there is more that needs to be changed and I'll want to test to make sure it works