Update set options to be stricter on when to exit

[kylecotter]

@markhuot @dreadfullyposh Any reason not to use set -euo pipefail for the main cog script?

In this example, the script did not exit as I was intending, where adding the above fixed it:

1. I have 2 cog commands, cog shell and cog build
2. cog shell is a wrapper for docker-compose exec node
3. cog build does a cog shell npm ci and a cog shell npm run build
4. if the cog shell npm ci exits for any reason, cog build continues on to cog shell npm run build when it should exit entirely

[markhuot]

No reason. It's an old script from before I knew about about all the options.

[mrw]

@kylecotter @markhuot I merged this in and launched it as part of v0.8.2, but rolled it back for v0.8.3 because there were a lot of unchecked variables etc that were causing the whole script to fail when -uo are in the set line. I'd like to see this made stricter/those options put in, but I think we'll need to check a bunch of that over before adding it again. Adding -v temporarily shows where it stops processing.