fix(success response handler): parse unsafe integers as strings

[fbeaudoincoveo]

JavaScript will automatically round integers that are outside of its "safe" bounds, i.e., from -(2^53 - 1) to 2^53 - 1, inclusive (±9,007,199,254,740,991). This means we'll lose precision if we convert values beyond those boundaries to integers.

The suggested fix is to return out of bound integers as strings, such that no precision will be lost.

Technically, this means that any number in a successful response body will be typed as a number (if it's safe) or as as string (if it's unsafe).

I decided not to adjust the response body interfaces, because this should happen only in a few exceptional cases (e.g., rowid / sysrowid, which are returned as very large integers).

Acceptance Criteria

• My changes are publicly available, documented, and deployed in production. (i.e. on Swagger)
• JSDoc annotates each property added in the exported interfaces
• The proposed changes are covered by unit tests
• Commits containing breaking changes a properly identified as such
• README.md is adjusted to reflect the proposed changes (if relevant)
• My merge commit message will be conventional (See Conventional Commit)

[toofff]

That's fine by me, if the @coveo/dx team is okay with the change.

[github-actions]

🎉 This PR is included in version 54.9.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀