gitlab-qa teardown fails when there is a ShellCommand::StatusError produces misleading stack trace

In https://gitlab.com/gitlab-org/gitlab/-/jobs/10018142871 gitlab was being misconfigured and would fail. However, teardown failed and a misleading stack trace is displayed in the job logs, making it difficult to debug. https://gitlab.com/gitlab-org/gitlab/-/jobs/10018142871#L175

The way gitlab-qa fails can be very misleading - We even have a message to point users to the logs but because of the error in teardown it was not displayed: https://gitlab.com/gitlab-org/gitlab-qa/blob/master/lib/gitlab/qa/component/gitlab.rb#L232-232