Exception message is not complete when using glue 3.0

[denys-tyshetskyy]

Describe the bug

When I am running glue-run for the glue 3.0 the exception returns very cryptic error message. Message is provided below.

When I switch to glue 2.0, the error becomes way more useful when it says that there is no access to default database and some lake formation permission issues.

Steps To Reproduce

Delete default glue database and/or remove LakeFormation permissions for the database that you are using in the dbt project.
Try to do dbt run on the pipeline which interacts with tables in the glue database

Expected behavior

Full error is displayed when glue 3.0 is being used

Screenshots and log output

Glue adapter: Glue returned error for statement None for code SqlWrapper2.execute('''/* {"app": "dbt", "dbt_version": "1.7.3", "profile_name": "...", "target_name": "dev", "node_id": "..."} */
drop table if exists ...'''), Py4JError: An error occurred while calling o89.toString. Trace:

System information

The output of dbt --version:

Core:
  - installed: 1.7.3
  - latest:    1.7.3 - Up to date!

Plugins:
  - glue:  1.7.0 - Up to date!
  - spark: 1.7.1 - Up to date!

The operating system you're using:
Windows

The output of python --version:
3.9

Additional context

Add any other context about the problem here.