feat: adds uint16, 32 and 64 formats

[baywet]

fixes #4564

[mikekistler]

Looks good! 👍

[lornajane]

Thanks for adding these

[karenetheridge]

This was created and merged so quickly I didn't have a chance to flag an issue with this...

There is no need for an integer type to be represented as a string in JSON (or YAML, or whatever other serialization format is being used). If the language/implementation/architecture cannot interpret the value as a native integer, then it can decode it into whatever makes sense for that architecture, and the format validation can then know that it is intended to represent a very large number for the purpose of its validation.

Allowing this value to be a string, for the purpose of encoding into JSON/YAML/etc, is not the right level of abstraction.

[baywet]

So then we should remove the string JSON data type from:

• uint64
• int64
• decimal
• decimal128

?

[karenetheridge]

Yes, I don't see why we need it, and it only adds complication.

[baywet]

Thanks for pointing this out! See #4588

[karenetheridge]

After a good conversation with @hudlow I have realized I was wrong here! I will open a new PR to correct this, with some more explanation.

edit: (I meant re #4588 - moving conversation there.)