Don't give Q any non-trusted tools in `--no-interactive` mode

[hayemaxi]

q chat will exit with an error in non-interactive mode if it wants to call a tool that isn't trusted. Instead, we should just not provide untrusted tools so it does not attempt to make the call. MCP tools included.

[hayemaxi]

"Partially trusted" tools will be tricky to handle in this situation (e.g. read only commands of execute_bash).

[swapneils]

"Partially trusted" tools will be tricky to handle in this situation

Could we expose partly-trusted tools and send an error message if the trust validation fails? IME when MCP servers themselves send errors, Q is fairly good at backtracking and trying something else.

(Your RFC for tool permissions would make this easier to accomplish)

[rationull]

#3256 is a very simple PoC of @swapneils suggestion, which I'm hoping can at least start a more concrete conversation about the desired UX here.