Exit Python Tests step after first failure

[dsubak]

Description (What does it do?)

Sets -e and -o pipefail on the python test wrapper script.

The practical effect of this is that if any of the scripts in the Python Tests section where this is executed fail, it'll immediately terminate execution and the last output in the github UI for that step will be the script with the non-zero status code.

By way of example, in this commit I artificially induced the detect_missing_migration.sh command to fail. As seen in the corresponding CI run, no subsequent tests are run and the output stops there.

Additional Context

This is pretty low stakes, but I do want to make sure this is desirable behavior. As written python_tests.sh kinda looks like the current behavior of carrying forward a failing status code but still executing the rest may have been intentional.

This proposed behavior was only very lightly discussed by Chris and I in this thread because we found earlier failures to be inadequately discoverable and thought this might be a good QoL improvement, but maybe there's a reason it's set up this way! Would welcome opinions or historical context.

[github-actions]

OpenAPI Changes

Show/hide ## Changes for v0.yaml:

## Changes for v0.yaml:


## Changes for v1.yaml:


## Changes for v2.yaml:

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).