setup() and teardown() errors and timeouts don't change the k6 exit code

[na--]

When there's an error in the setup() or teardown() function or when they time out, k6 will abort the script execution and print something like ERRO[0000] Engine error error="setup: Error: my_intentional_error at setup (...) or ERRO[0010] Engine error error="setup: context cancelled at setup (...)", but the actual exit code of k6 itself will still be 0, as if everything is OK.

This is in stark contrast to errors in the init code, which immediately abort k6 and change the exit code to 255. The actual error code is subject to future change, the important point is that it's not 0. The setup() and teardown() functions should behave the same way, since there's no concurrency with their execution, it's just a single transient VU executing them and it's important for users to have feedback that something went wrong during their execution.

[na--]

Just as as pointer when we fix this, this is where we log the error and stop the script, but we don't change the actual exit code.

Also, as mentioned in this issue, it'd probably be worth it if these errors had their own specific exit codes.