Task doesn't fail when using "set -e" or "return" without parameter

[stylemistake]

Something is seriously broken here, need to investigate.

Easiest way to reproduce is to check task_publish-npm() function in runnerfile.sh.

Right now, npm publish || return "${?}" form is used, which errors out just fine, but npm publish || return does not error out. In fact, it returns 0 every time.

Will add tests someday, because this issue pops up multiple times.

[stylemistake]

Currently the best solution seems to avoid conditional operators (||, &&) at all costs when chaining commands inside the "runner" itself, because they forcefully reset the set -e flag which you can't re-enable later.

It seems I have done a good job at keeping the next branch clean of such things. We can finally use set -e inside tasks, so you no longer need to write <command> || return ${?} everywhere.