fix: invalid float number format by json-bigint

[justinpark]

SUMMARY

In #21968, it replaces the json-bigint by json-bigint-native to fix the invalid float number handling by escaping BigNumber(BigInt) wrapper.
However, json-bigint-native uses native BigInt only which has limit compatibility of Math functions that throws TypeError several cases.

This commit reverts the commit in order to keep it back to use BigNumber (which is compatible with Math functions).
Instead it adds a custom logic to escape the BigNumber for floating numbers. It also adds a todo comment to fix the root cause by open source in the future.

cc: @john-bodley @ktmud @villebro @zhaoyongjie

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before: (returns NaN values)

After:

TESTING INSTRUCTIONS

Create a chart with floating numbers

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[ktmud]

Can we just inline this?

      // `json-bigint` could not handle floats well, see sidorares/json-bigint#62
      // TODO: clean up after json-bigint>1.0.1 is released
      json: cloneDeepWith(json, (value: any) => (
          value instanceof BigNumber && !value.isInteger() ? Number(value) : value)
      )),