Track client-originated query errors separately from server errors in sql-server logs

Currently, errors from bad or invalid client queries are logged at the same level as real server errors in `dolt sql-server`. This makes log-based alerting noisy. A client sending malformed queries can fill disk with errors that operators cannot act on.

Common examples of client errors that should not appear as server errors:
```
CALL DOLT_COMMIT('-m', 'msg') -- with nothing staged
CALL DOLT_BRANCH('existing-branch') -- branch already exists
-- etc
```

The fix belongs in GMS. MySQL likely has precedent here worth checking. The goal is that operators running a sql-server only see actionable server errors by default; client errors should be suppressed or logged at a lower level, with an opt-in mode for debugging.