Our automated testing jobs currently use different sets of compiler warning flags when building. Sometimes that's necessary for the functionality of the test, but generally we should switch to using our defined set of "as strict as possible" compiler flags that are available via configure --enable-strict.

The goal of this ticket is to review our automated test suites and convert to using --enable-strict where it makes sense.