Guard against compiler warnings, second try

The compiler needs optimization flags to actually report the kinds of warnings we're looking for in ngen's CI.

Follow-on to #35 after I realized the above

Changes

Compile with minimal optimization to generate warnings that depend on control/data-flow analysis
Make the shell scripts more particular about stopping on errors, rather than just letting them flow through.

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (link if applicable)
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] Visually tested in supported browsers and devices (see checklist below :point_down:)
[x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[x] Reviewers requested with the Reviewers tool :arrow_right: