Structured errors for parsing overflowing ints

[dpetrick]

Related issues:

• Cannot insert Floats (≥9.223372037e18 and <1e21) or (>-1e21 and ≤-9.223372037e18) prisma#12651 (only partially addresses this ticket!)
• Prisma panic on invalid int prisma#12526
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#12737
• Engine hard crashes on id values exceeding the Number.MAX_SAFE_INTEGER prisma#12841
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#12491
• PANIC: called Option::unwrap() on a None value in query-engine\core\src\query_document\parser.rs:250:87 prisma#10586
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#12654
• Huge Int value in upsert causes: "PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87" prisma#10049
• Client crash on out-of-range integer update using Postgres prisma#12969
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#11467
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#11263
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#9896
• PANIC: called Option::unwrap() on a None value in query-engine/core/src/query_document/parser.rs:250:87 prisma#13293

Makes sure the engine doesn't crash on encountering an integer serialized as float that is outside of the i64 range (surfaced as P2009). Introduces a less concrete P2033 error code for when the GraphQL parser errors on an int that doesn't fit. The reason for the separate error is that we have very little actual information on that parsing stage, plus the later parsing error (where the unwrap tickets point to) is on a completely different layer with more info, which can't easily be propagated as a different error code than the enclosing parser error (P2009).

Example P2009:

Unable to fit float value (or large JS integer serialized in exponent notation) '100000000000000000000' into a 64 Bit signed integer for field 'int'. If you're trying to store large integers, consider using `BigInt`

Example P2033:

A number used in the query does not fit into a 64 bit signed integer. Consider using `BigInt` as field type if you're trying to store large integers.

[Weakky]

I'm flooded with serotonin seeing all those issues about to be closed. Nice impactful work, lgtm 👍

[garrensmith]

This looks good to me. Once you fixed the clippy complaints this should be good to go.