fix: improve error message output in integration tests

[gfanton]

This PR improves error output in integration tests by using more verbose format.

gnokey will now display the full stack trace log, including the underlying error, when an error occurs, instead of only presenting the top-level error.

This enhancement will assist in better debugging what's happening without the need to delve directly into gnoland logs.

Contributors' checklist...

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests
• Added new benchmarks to generated graphs, if any. More info here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7d66398) 55.94% compared to head (3b22cd9) 55.59%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1349      +/-   ##
==========================================
- Coverage   55.94%   55.59%   -0.35%     
==========================================
  Files         420      420              
  Lines       65415    65413       -2     
==========================================
- Hits        36596    36369     -227     
- Misses      25961    26197     +236     
+ Partials     2858     2847      -11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[moul]

I prefer the new output 👍

Can you check how much we could improve the package/errors instead of avoiding using it?

[gfanton]

@moul sure ! Let me check

[gfanton]

I've reverted my changes and will simply use "%+v" instead of "%v" for the integration tests. It took me a while to notice that we are using a custom format for our errors. For now, this change is sufficient as my main goal was to improve the error output of the gnokey command within the integration tests.

That said, I believe there is room for improvement in error handling, as we should not need to use this kind of format to obtain the source error. Do you think we can update our errors package to use a more recent format, wrapping %w, to improve error readability? (in a separate pull request)