fix(cubesql): Propagate errors from SqlAuthService to the user

[KSDaemon]

When using cube.py it’s fundamental to see errors and even better the stack trace of errors generated from python code, currently the logs doesn’t show any errors generated from python check_sql_auth.

This PR propagates such errors to the log.

Imaging this cube.py config:

# Validate the username and password of the user submitting the API request
@config('check_sql_auth')
def check_sql_auth(query: dict, username: str, password: str) -> dict:
  raise Exception('You should be able to see this error in the logs')

And let's try to connect to Cube via psql:

❯ psql -h 127.0.0.1 -p 15432 -U cube
psql: error: connection to server at "127.0.0.1", port 15432 failed: FATAL:  password authentication failed for user "cube"

And here is what we now can see in logs:

cubejs-server
🔥 Cube Store (1.3.19) is assigned to 3030 port.
🔓 Authentication checks are disabled in developer mode. Please use NODE_ENV=production to enable it.
🦅 Dev environment available at http://localhost:4000
🔗 Cube SQL (pg) is listening on 0.0.0.0:15432
🚀 Cube API server (1.3.19) is listening on 4000
Auth Error: undefined
{}
Error: Python error: Exception: You should be able to see this error in the logs
Traceback (most recent call last):
  File "cube.py", line 14, in check_sql_auth
    raise Exception('You should be able to see this error in the logs')

Check List

• Tests have been run in packages where changes made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet

[codecov]

Codecov Report

Attention: Patch coverage is 18.18182% with 9 lines in your changes missing coverage. Please review.

Project coverage is 84.17%. Comparing base (91d57de) to head (4799615).

Files with missing lines	Patch %	Lines
...ubesql/cubesql/src/sql/postgres/pg_auth_service.rs	18.18%	9 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #9665       +/-   ##
===========================================
+ Coverage        0   84.17%   +84.17%     
===========================================
  Files           0      230      +230     
  Lines           0    85114    +85114     
===========================================
+ Hits            0    71647    +71647     
- Misses          0    13467    +13467     

Flag	Coverage Δ
cubesql	84.17% <18.18%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ovr]

It's just another problem related to how users write check_sql_auth.

Default example from the documentation:
https://cube.dev/docs/product/configuration/reference/config#check_sql_auth

It will throw an exception for incorrect username/password, but the biggest problem is that we will start to spam it in our logs.

[KSDaemon]

I don't think it's a problem. In a common standard flow, there will be no exceptions thrown as every real good user would be authorized and logged in. While any auth denial is an outstanding event and might be a reason to look into it.

[ovr]

cC @igorlukanin