Fix emscripten CI after recent emsdk change

[sbc100]

See emscripten-core/emsdk#472

Turns out we were actually depending on the non-embedded
config!

[kripken]

Ah, this worries me that more users will break then...

I assume the plan is to switch CI to embedded, but it would take more work than makes sense to do right now to unbreak? (how much work is that?)

[sbc100]

I agree there could other unexpected fallout. That is why I will leave the --no-embedded option in there for a while until we can figure out all the use cases.

Our use case is pretty weird here. We use emsdk here but never call ./emsdk_env.sh which means none of the emsdk environment variables get set... and then we expect to be able to use our own version of emscripten it. But I think we can figure out way to switch to the embedded config here anyway.

[sbc100]

Yes.. exactly .. unbreak first.. then look at making the switch.