Support added for exceptions with ASYNCIFY

The general scheme is not very complicated. Changes:

1. Rather than doing `dynCall_vi` on the *foo*__asnc_cb function, we use `invoke_vi`. This is essential if the callback functions are to throw exceptions.
1. If a callback did throw an exception, then we should reenter the parent callback function only if it checks for exceptions at the resume point. Otherwise, the exception should propagate up. We check for this using an extra boolean in the async context: `emscripten_alloc_async_context` now has an extra argument which the C++ code uses to indicate whether the async function is called with "invoke" or "call". (So the `invoke` argument to `emscripten_alloc_async_context` is set when `__THREW__` is checked immediately after the async call.)
1. If the exception isn't caught anywhere, we rethrow it finally so that an error message is provided (admittedly not a very clear one, but it's no worse than when an exception is throw out of a synchronous `main`).

This pull request works in conjunction with the pull request to the fastcomp compiler.
Well how about this then?

    int test_fn() {
      emscripten_sleep(10);
      int* test = (int*)alloca(20);
      test[0] = 42;
      emscripten_sleep(10);
      return test[0];
    }

It doesn't do what you want! The variable "test" causes the realloc to try and allocate a bigger async context, which tramples on the memory the application developer is trying to use. There's nothing stopping people from calling alloca in an __async_cb function, and I bound someone's eventually going to try to port a library that does that to emscripten.

In any case, emscripten offers and `alloca.h` header and purports to support it, so it should print a clean assertion failure if someone does use it with asyncify.