fix: prevent stack trace on the course of error

[jamesgeorge007]

It is difficult to debug when the workflow fails since the internal stack trace is what gets logged currently. For instance, #112. This PR aims at fixing this behaviour by logging the content of the stderr stream instead.

Before

After

[tuunit]

I'll give this a review tomorrow ;)

[tuunit]

LGTM

[jamesgeorge007]

@tuunit, let's use squash and merge unless the PR includes commits from multiple authors, for instance, #97.

[tuunit]

@jamesgeorge007 so you want to always squash every merge to a single commit with a message following conventional commits correct? Regarding multiple authors. Do you want to keep multiple commits and change each commit per author to a conventional commit message or do you want to squash it as well and just add @Co-authored-by username? https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors

[jamesgeorge007]

When multiple PRs get merged to a feature branch and thereafter to the default branch let's preserve the individual commits and use rebase and merge like in the case with #97. The idea is to have one commit associated with a feature.

In other cases, let's use squash and merge (regardless of it is to the default/feature branch) like with the case of this PR.