Fix logging from llama-llava-cli

[Googulator]

Use the actual logging facilities from common, instead of bespoke LOG_xxx() macros that unconditionally print to stdout/stderr.

The actual response is printed with printf(), so --log-disable won't also swallow the response.

• I have read the contributing guidelines
• Self-reported review complexity:
  • Low
  • Medium
  • High

[ggerganov]

The llava/clip.cpp and llava/llava.cpp should not depend on libcommon.

[Googulator]

Isn't the whole point of having a library named "common" is that any component (that's not itself a dependency of libcommon) can use it?

[ggerganov]

The libcommon is intended to be used only by the examples and not by libllama. The llava and clip code is potentially going to be merged in libllama in the future, so that's why we should keep it decoupled from libcommon.