Console shows misleading connection error instead of actual import failure details

[objectiveous]

Problem

When a database import command fails, TypeDB Console displays a misleading connection error message instead of the actual failure reason. This is particularly confusing because the console is already successfully connected to the server, making the error message factually incorrect and unhelpful for debugging.

Steps to Reproduce

1. Successfully connect to TypeDB server via Console
2. Execute: database import foo ./cached_github_schema.typeql data.typeql
3. Observe the misleading error message when the import fails

Current Behavior

Console shows:

Error executing command: 'database import foo ./cached_github_schema.typeql data.typeql'
[CXN03] Connection Error: Unable to connect to TypeDB server(s), received errors: 
- dots.dots:1729: Request generated error

The "Unable to connect to TypeDB server(s)" message is misleading since the console is already successfully connected to the server.

Expected Behavior

Console should display the specific import failure reason. The server logs show more detailed information:

Import to 'foo' finished without completion after 0 seconds.

Console should surface the actual cause of the import failure (e.g. schema validation errors, file format issues, permission problems, etc.) instead of masking it as a generic connection error.

Environment

• TypeDB Console: Latest version
• TypeDB CE: 3.4.0
• Server logs show the import attempt but no specific failure details

Impact

• Makes debugging import issues extremely difficult
• The misleading "connection error" message confuses users who are already connected
• Users waste time troubleshooting non-existent connection issues instead of the actual import problem

[farost]

The connection error is just a general wrapper around the errors, and it's not very good, I agree. It was something we wanted to refactor soon.

However, database import should return all the detailed causes after this connection error header, unless something very critical and weird happened.
Request generated error looks like a generic HTTP error we could not recognize, so there is probably indeed a connection error. But I'm interested to hear more about what has actually happened

[flyingsilverfin]

Thanks for the report @objectiveous - do you think you could give us a reproducible scenario for this? Then we can fix it very quickly im sure!