fix: Don't display int64 range in docs

[SB-harshitajadhav]

Motivation and Context

STOP-231

Description

Previously range was getting displayed without being defined in the schema for int64.

How Has This Been Tested?

Tested locally by doing yalc in Platform internal.

Screenshot(s)/recordings(s)

Before

After

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• This PR's code follows as closely as possible the coding style/guidelines of this project.
• I have added error reporting and followed the error reporting guidelines.
• I have added event tracking and followed the event tracking guidelines.
• I have updated any relevant documentation accordingly to reflect this PR's changes.
• I have added automated tests (unit/integration/e2e/other) to cover my changes.
• All new and existing tests pass locally (excluding flaky CI tests).

[prafullaAtSB]

Good to go ahead with these changes.
Add more explanation of root cause and area where it is failing in the documentation.

[bhaskarsontakke]

As mentioned by Prafulla, please provide the detail why we have removed int64 min/max calculation. changes looks ok to me

[SB-pradeep-bande]

Looks good to me.

[stoplight-bot]

🎉 This PR is included in version 4.16.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀