Use json-bigint for Integer Parsing

[ItzNotABug]

What does this PR do?

Fixes the issue where the big integers are incorrect due to precision loss.

Fixes appwrite/console#1473

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

• 🐛 Bug Report: Appwrite Dashboard -> Invalid max param: Value must be a valid integer & Attribute with the requested ID could not be found console#1473

Have you read the Contributing Guidelines on issues?

Yes

[stnguyen90]

@TorstenDittmann, you okay with taking this approach?

[loks0n]

Can you share more about the issue? What situation does it occur?

[loks0n]

Do we need a depencdency? is it possible without?

[ItzNotABug]

Yup. I don't think there's a built-in logic for managing big-ints.

[ItzNotABug]

Can you share more about the issue? What situation does it occur?

The values returned on console are different for min/max due to how PHP and JS round off the int/big int. Values should be -
-9223372036854775808 & 9223372036854775807 but JS rounds off to -9223372036854776000 and -9223372036854776000. This causes issues during updates iirc.

[ivanskodje]

Fixes the issue where the big integers are incorrect due to precision loss.

Does these changes affect how the Console repo parses the number it receives from the backend? I ask, because in Console we are already receiving the correct number from the backend via JSON - but it is only after it parses it into a number object it gets rounded to an incorrect amount causing this issue.

Ref: appwrite/console#1473