[DataStore] Inconsistent support for min/max integer values

[Jordan-Nelson]

Describe the bug
Datastore has inconsistent support for the max/min values that can be stored for for integer types. The following mix/max values are supported in each platform.

iOS Max: 2^53 (larger values can be saved, but the incorrect value will be returned when queried)
iOS Min: -(2^63) (min 64 bit int)
Android Max: 2^31 - 1 (max 32 bit int)
Android Min: -(2^31) (min 32 bit int)

To Reproduce
Steps to reproduce the behavior:

1. Create a sample app with a model that has an int value
2. Save a model that has a value larger/smaller than the values listed above
3. Query the model and compare it to the saved value
4. The queries will either fail, or the value will not save correctly

Expected behavior

• Both platforms should support the same min/max values
• max/min 64 bit 32 bit integers should be supported
• attempting to save a value small/larger than the min/max value should fail with a clear exception

Platform
Amplify Flutter current supports iOS and Android. This issue is reproducible in (check all that apply):
[x] Android
[x] iOS

[EricRenForCode]

I am trying to save a large Int value into my Model. And if the Int value is large but smaller than 2^32-1, the DataStore.save() function saved successfully in Local, but failed to sync in Cloud. I finally change my Model filed type from Int to String to fix this issue.

[HuiSF]

According to AppSync documentation, the scalar type Int range is between -(2^31) and 2^32-1.

Would probably add a client validation in iOS to prevent value being out of range.

@EricRenForCode That should be expected behavior as what the documentation pointed. If you need a bigger range to record the number, using String type may be a good choice.

[Jordan-Nelson]

As noted in #4318 (comment), the DX could be improved by throwing a clear error message when the number exceeds the min/max value.