Langroid

fix: OpenAICallParams.top_p: change type to float

fix: set litellm.modify_params=True to accommodate quirks of non-OpenAI APIs without crashing.

(E.g. Anthropic APIs don't support first msg w system role)

fix: Further enhances of json parsing from tool-gen with weak LLMs

fix: Improve JSON parsing (e.g. code) from weak LLMs

Uses the excellent, lightweight [json-repair lib](https://github.com/mangiucugna/json_repair).

One example where this helps: when using tools, weak LLMs sometimes generate JSON that has un-escaped newlines within strings.
If we simply discard these, it's problematic when the strings contain newline-sensitive code (e.g. python, toml).
Instead we should escape these newlines, but ONLY escape the newlines that appear within string-valued fields in the JSON
(newlines that appear outside of these should definitely NOT be escaped, or it leads to inaccurate json).
Fortunately, the excellent json-repair lib has a good solution for this and other pesky json issues, using CFGs.

fix: in logging.py, escape markup when using rich.console.print(...)

fix: switch to langroid-tools for o1 models since they don't yet support tools/fns in API

When using o1 models, the `ChatAgent` automatically sets `ChatAgentConfig.use_functions_api` to False,
and `ChatAgentConfig.use_tools` so that Langroid's prompt-based ToolMessage mechanism is used instead.

feat: TaskConfig.recognize_string_signals bool flag (default True), can be set to False to dis-allow string-based signals like DONE, PASS etc

This is useful when we want to avoid "accidental prompt injection" (e.g. "DONE" may appear in normal text, and we don't want that to trigger task completion).
In general it is preferable to use the task orchestration tools (`DoneTool` etc) rather than string-based signals.