Inconsistent behavior between JS and Rust SDK

[ardatan]

While porting the test from https://github.com/graphql-hive/console/blob/main/packages/libraries/core/tests/usage.spec.ts#L193 to Rust;
I realized that JS SDK doesn't send this one with !;
https://github.com/graphql-hive/console/pull/7364/files#diff-e95ef9e6aaeb5b11afa8ba0d1d6c31778caaaab15eef6f3259227a705dd55ac7R405

[jdolle]

We can opt to make the JS implementation match the Rust implementation, or make Rust match JS.

---

This is the one case that isn't very well defined in the current logic.
We have a required input argument as a variable, but that variable isn't being passed when calling the operation. This request will fail anyway you look at it, but do we track this input as provided by the client, because it's required? Or do we track it as not provided, because it actually wasn't sent?...

The only time this matters is if you start with a required argument, send some data, push a breaking change to make it nullable, then want to go back to required. So, I consider this an extreme edge case, but it would be good to be consistent.

The function that determines whether or not this value is checked is https://github.com/graphql-hive/console/blob/main/packages/services/api/src/modules/schema/providers/registry-checks.ts#L905

Due to this being such an edge case, I don't have any preference over which approach we choose.