Wasm backend testsuite failure: trivial failures caused by prefixed ghc

There are a couple of trivial testsuite failures that look like:

-ghc: unrecognised flag: -fflul-laziness
+wasm32-wasi-ghc: unrecognised flag: -fflul-laziness
-ghc: on the commandline: missing argument for flag: -drule-check
+wasm32-wasi-ghc: on the commandline: missing argument for flag: -drule-check
-ghc: on the commandline: missing argument for flag: -I
+wasm32-wasi-ghc: on the commandline: missing argument for flag: -I

The stdout normalization logic of the testsuite driver hasn't taken the cross GHC prefix thing into account yet.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information