Feat - error handling

[b-ma]

Quite a massive one again,

Still need to

• Handle simple errors that may occur here and there and that comes from the bindings, e.g.

[lib/errors.js] Unhandled error type Error undefined value for ChannelInterpretation
  | X new WaveShaperNode(c, {channelInterpretation: "foobar"}) threw "Error" instead of EcmaScript error TypeError.

• Wrap the AudioParam interface
• Wrap the AudioBuffer interface, but will do that later, not sure how to handle this case right now

Results so far:

  RESULTS:
  - # pass: 3740 (+135)
  - # fail: 1281 (-3)
  - # type error issues: 109 (-125)

[b-ma]

RESULTS:
  - # pass: 3863 (+123)
  - # fail: 1208 (-73)
  - # type error issues: 59 (-50)

With:

• Fix AudioParam behaviour orottier/web-audio-api-rs#424
• fix: unwanted panic at Analiser initialization orottier/web-audio-api-rs#422

[b-ma]

Ok let's merge, that's already a lot of stuff (and improvements)

[orottier]

Hey yeah sorry, I had not taken the time yet to look into this.
Do you want me to rewrite all user facing panics as <JSErrorName> - <ErrorMessage> ? Some of them still use : as separator

[b-ma]

No problem, the diff is mostly unreadable anyway :)

In short, we now have JS facades for almost every nodes / classes (still need to handle AudioBuffer and PeriodicWave I guess) which are mostly there to catch native errors and re-trigger them with the right error type.

Do you want me to rewrite all user facing panics as - ? Some of them still use : as separator

Yup that would be nice indeed! Thanks

Also made some update this morning to use the new async resume, suspend, close methods, seems to work like a charm!