ci(tests): Improve the handling of failures during the workflow

[gustavotrott]

This PR aims to improve the handling of failures during the automated-test workflow.

Currently, most of the commands run inside a block like this:

sudo sh -c '
            command 1
            command 2
            command 3
'

As it turns out, if command 2 fails and command 3 succeeds, the Step will still be marked as Successful. However, the correct behavior would be for it to fail!

So, I've tweaked most of the steps to run in a block like this:

sudo -i <<EOF
            set -e
            command 1
            command 2
            command 3
EOF

In this way, if one of the commands fails, the Step will be marked as a Failure. This will help us identify where the problem lies.

Additionally, I've tweaked the wget command to use the -nv (non-verbose) parameter instead of -q. This is because -q was suppressing the error message, making it more difficult to pinpoint the problem.

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
8 Code Smells

No Coverage information
3.2% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint