### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

Adjust Tool Permission Guardrail logging so expected/non-actionable events are not emitted at `WARNING` by default.

Specifically: - Change `Tool Permission Guardrail: not running guardrail. No tools or functions in data` from `WARNING` to `INFO` or `DEBUG` - Consider changing denied-by-rule messages from `WARNING` to `INFO`, or make the log level configurable

Confirmed on the current `main` branch in:

`litellm/proxy/guardrails/guardrail_hooks/tool_permission.py`

that both: - the “not running guardrail” path - the denied-by-rule paths in pre-call / post-call / streaming post-call

currently use `verbose_proxy_logger.warning(...)`.

### Motivation, pitch

These messages can be expected during normal operation and generate excessive log noise.

Examples: ```text Tool Permission Guardrail: not running guardrail. No tools or functions in data Tool Permission Guardrail: Tool 'manage_resource_alpha' denied by rule 'block-restricted-tools' ```

Operationally, these do not always warrant `WARNING`: - If a request has no tools/functions, skippi…