Switch to serde-wasm-bindgen over serde-serialize feature

[Aaron1011]

The serde-serialize feature is deprecated
(rustwasm/wasm-bindgen#3031).

This solves a cyclic dependency error with aHash

[relrelb]

Can you please prefix the commit message with web:?

[Toad06]

Not sure if this is related to this PR but the user's configuration is completely ignored in the current nightly build (2022-09-25), both self-hosted and extension versions are affected.

For instance, if you set the log level to "Info" using the extension, this won't trace anything but the errors which is the default (note: there are some traces but they come from the JS file which is not affected by the config). wmode="transparent" also won't work, etc.

The issue only seems to happen when at least one of the option is not specified on the Javascript's object that holds the config.

[relrelb]

Not sure if this is related to this PR but the user's configuration is completely ignored in the current nightly build (2022-09-25), both self-hosted and extension versions are affected.

For instance, if you set the log level to "Info" using the extension, this won't trace anything but the errors which is the default (note: there are some traces but they come from the JS file which is not affected by the config). wmode="transparent" also won't work, etc.

The issue only seems to happen when at least one of the option is not specified on the Javascript's object that holds the config.

Wow, thank you! That's quite an embarrassing regression... Anyway I tossed out a fix in #8093. I confirmed it to work on my end using the demo page, but you're more than welcome to double-check the other components (JS API, extension etc.).
I think we definitelty need to cover this with tests, to avoid future regressions.