fix(cli): error handling

[Piskoo]

This PR grcp errors not being properly caught and replaced with more user friendly error in CLI.

Closes #2434

[migmartri]

mm, this looks like a little bit of a hack that could cause false positives. Do you know when and why this started failing? Was it because we are now wrapping when we should not?

[jiparis]

The error in backend might have changed. It was a hack already anyways, since it was comparing error strings in client side, instead of just the error code or a typed error object.

[migmartri]

Example
Before it was checking for equality between JWT token has expired and rpc message JWT token has expired metadata = map[] cause =

So what's now?

Will be be reverted to what originally was which was handled locally as I mentioned in the issue?

[Piskoo]

I'll work as it did before, seems like part of the output was missing in the description and I didn't notice. In general the problem is that grpc status returns message that looks like full error instead of only returning the message part:

rpc error: code = Unauthenticated desc = couldn't match JWT provider: error: code = 401 reason = UNAUTHORIZED message = JWT token has expired metadata = map[] cause = <nil>

Which then before was matched against JWT token has expired . It resulted in inequality so the error was not replaced in the end. Not sure when and why is started, but it's probably related to grpc-go being updated at some point. Went through Kratos and grpc and no changes were made to related files. Some backend change must have changed it

[migmartri]

This is the actual fix #2450 so I'd suggest closing this one.