Dump FIPS check script log on failure for actionable error reporting

When fips-check-PILOT.sh or fips-check.sh exits non-zero, cat the captured
log to stdout instead of leaving the user with just the rc value and a log
file they may not have access to (e.g. inside a Jenkins workspace). The
preceding redirect on line 229 uses single '>' so LOG_FILE at this point
contains only the failed script's output. Diagnostic-only change; success
path is unchanged.

Author: aidangarske

scripts/utils-wolfssl.sh

@@ -235,6 +235,11 @@ install_wolfssl() {
                 fi
                 if [ $RET_CODE != 0 ]; then
                     printf "ERROR checking out FIPS (return code: $RET_CODE)\n"
+                    if [ -f "$LOG_FILE" ]; then
+                        printf "\n--- %s output: ---\n" "$fips_check_script"
+                        cat "$LOG_FILE"
+                        printf "--- end %s output ---\n\n" "$fips_check_script"
+                    fi
                     rm -rf ${WOLFSSL_INSTALL_DIR}
                     do_cleanup
                     exit 1