graph, graphql, store: Coerce Int8 values to ints

[lutter]

Previously, they were coerced to strings which ultimately leads to errors when lists of int8 are used in queries

@dotansimha Do you remember why Int8 was initially coerced into String in a lot of places? The whole topic of coercion is really confusing to me; part of it is because the Value of graphql-parser can't represent all the values we deal with internally (like bytes or int4 vs int8) and so you are forever trying to figure out if a string is really a string or whether it's a byte array. The other part is that coercion happens all over the place and it's really hard to draw a line between 'here we are dealing with values that have fairly random types and aren't checked yet' vs 'these values have been properly checked and express the proper type'. I wonder if we should expand the r::Value type to faithfully represent all value types, and take the conversion from q::Value to r::Value as the point where we go from unchecked to checked.

[dotansimha]

@lutter I think the max value of i64 is 9223372036854776000 and this number is too big to be represented in JavaScript runtimes, so we need to use BigInt values (that are de/serialized as String).
Also check wasm-bindgen/wasm-bindgen#35

[github-actions]

This pull request hasn't had any activity for the last 90 days. If there's no more activity over the course of the next 14 days, it will automatically be closed.

[lutter]

Closing this since it's not been active for a while. Feel free to reopen when you're ready to work on this again