`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

首先检查 JSKit 对 Web API IDL long long 值的处理方式，并将 issue 中提到的 AudioData、Blob 和 File 属性与 wasm-bindgen issue 800 进行比较。要视为完成，需要确定 JavaScript 数字的表示方式，并通过测试确认这些属性是否支持 BigInt；没有指定实现文件或测试。