Unmask catch-all token exceptions

[0x2b3bfa0]

Masking all the errors derived from this function is highly counterproductive in some edge cases. At least, bad credentials and not found are common but separate errors, and mixing them can lead to long and frustrating blind debugging sessions.

CML components rely heavily on services we don't control, and errors are hard to reproduce and hard to trace. While the happy path should be as pretty as possible for end users, errors should be as verbose as possible and contain as much useful non-sensitive information as we manage to extract.

As @DavidGOrtega suggested, we may also implement some sort of wrapper and print a few suggestions for the possible causes for each error, but outputting the original error message is a must.

See also

• self-hosted runner not connected to my repo. #562 (comment), how this pull request converts a blind debugging nightmare into an immediate solution.
• lint: fix camelCase #554 (comment), extended discussion about the topic.

[DavidGOrtega]

👍

[DavidGOrtega]

We have a couple of this also. One is regarding the GL endpoint @0x2b3bfa0

[DavidGOrtega]

@0x2b3bfa0 #472