checking ollama client/version compability

[maxandersen]

While testing on two laptops the last two weeks I was discovering various issues caused by ollama version differences.

On laptop 1: could not run granite3-dene well. seem ollama itself was "stuck" at 0.3 version because I never restarts my laptop. Once I noticed ollama had an update available (its only visible in the menubar if you click on it) I got 0.4 and things got better

On laptop 2: the ollama client was installed with brew but ollama server was the main ollama binary. Resulting in me running a 0.1 ollama client, ollama 0.4 server. And had all such of problems.

Just like #101 where ollama version mismatches can be problematic we should look into either shipping our own ollama or at least check if versions align/are within a supported range.

[maxandersen]

p.s. you get info like this when running ollama -v :

ollama client available, server not running:

ollama -v
Warning: could not connect to a running Ollama instance
Warning: client version is 0.4.1

ollama client available, server not running:

ollama -v
ollama version is 0.4.1
Warning: client version is 0.1.3

(above is not verbatim copy but just from memory - thus replicate the scenario, don't implement based on that pattern of text)

ollama server and client aligned:

ollama -v 
ollama version is 0.4.1

from that we could warn/ suggest updates.

[fbricon]

@neehar18 this is an extension of #101