SPIKE: better errors in Freighter client

[aristidesstaffieri]

We handle displaying errors in a few ways -

1. Show the raw error and/or stack trace to the user.
2. Show a generalized error.
3. Show a user friendly error message mapped to error codes or types.

Can we improve the UX here? Can we stop showing raw rpc errors and/or stack traces to users? Should we implement a client only tracing system, where we can provide users trace IDs in their error messages that they can use to communicate their issues. We can then use the IDs to correlate the report to a log.

[JakeUrban]

@aristidesstaffieri I recognize it might be difficult but if possible, can we get screenshots of the 3 error cases you described here?

I definitely don't think we should ever provide stack traces or raw response bodies from upstream systems.

[JakeUrban]

@aristidesstaffieri is this issue redundant now that you've created tasks for the tech debt epic?

[aristidesstaffieri]

Yes that makes this a duplicate, closing in favor of that epic.