`JSNumber` type to support `long long` type in Web API IDL

Rust folks have a similar issue, where long long shouldn't be mapped to Int64, which is bridged to BigInt on JS side. https://github.com/rustwasm/wasm-bindgen/issues/800

Checked a few other places where long long is used, like AudioData, Blob, and File and all of them return a JS number in corresponding properties, not BigInt. I'm 95% sure none of these support BigInt, remaining 5% certainty could be added by writing actual tests. I personally vote for either keeping these Int32 as proposed, or creating a new union type. Just riffing:

enum JSNumber: ExpressibleByIntegerLiteral, ExpressibleByFloatLiteral {
case integer(Int32)
case float(Double)
// ...
}

Should we add such type to JSKit then?

cc @kateinoigakukun

Originally posted by @MaxDesiatov in https://github.com/swiftwasm/WebAPIKit/issues/42#issuecomment-1125355976

Inizia esaminando come JSKit gestisce i valori long long di Web API IDL e confronta le proprietà di AudioData, Blob e File menzionate nell’issue con wasm-bindgen issue 800. Per considerare il lavoro completato, sarebbe necessario decidere una rappresentazione per i numeri JavaScript, insieme a test che confermino se queste proprietà supportano BigInt; non viene indicato alcun file di implementazione né alcun test.