i/usize types should generate bigint when in 64-bit systems

[escritorio-gustavo]

Goal

Export bigint for usize, isize and their NonZero counterparts when in a system with 64-bit pointers Closes #311

Checklist

• [x] I have followed the steps listed in the Contributing guide.
• [x] If necessary, I have added documentation related to the changes made.
• [x] I have added or updated the tests related to the changes made.

[NyxCode]

I'm really unsure about this.
For the use-case I most often have in mind - JSON APIs - this would be super weird, since there's no correlation there.

Am I missing something here?

[escritorio-gustavo]

This is kind of part of the debate going on in #94 about number/bigint. Since we consider numbers with 64+ bits as bigints #311 argues we should also consider i/usize as bigints on systems with 64 bit pointers

[escritorio-gustavo]

This does affect JSON APIs, the creator of #311 commented that his API attempted to send a usize to the frontend, which failed to parse it because JS numbers can't handle usizes, causing a runtime error