fix: allow null parameter types; loosen QueryParameterValue marshalling

[ohaibbq]

We need to depend on the published generated protos for the BigQuery API. These protos type QueryParameterValue.Value as a string which is not compatible with how the Python/Node clients send the parameters. This implements custom marshalling to handle cases of null, boolean, and numeric values.

closes #58
closes goccy#312
closes goccy#234
closes goccy#137

[djohnson-aperture]

There's a small edge case here. int is not interpreted correctly.

Error: failed to analyze: INVALID_ARGUMENT: Type not found: int [at 18:121]

Workaround is to replace int with int64. Once again, this does work with a production BigQuery table.

Edit:
Sorry I just realized that issues is in how the query property is parsed, not the parameters. Should I flag another issue for this comment's issue?

[ohaibbq]

zetasql doesn't recognize quite a few type aliases. I'm unsure if the latest version supports adding these type aliases.
You'll want to use INT64 in your queries.

I've been looking into updating the go-zetasql bindings and am slowly making progress there.

goccy#195
goccy#88