When using BrowserCompatible, BigDecimal in the Double range behaves the same as Double. for issue #3123

[rowstop]

What this PR does / why we need it?

Summary of your change

public static boolean isJavaScriptSupport(BigDecimal decimal) {
        boolean jsSupport = decimal.precision() < 16 || isJavaScriptSupport(decimal.unscaledValue());
        if (!jsSupport && decimal.scale() != 0) {
            //Use double for comparison
            //double and javascript number have the same precision
            //In extreme cases, precision loss may occur.
            //There will be a loss of precision between [4.9e-324, 5e-324), which will be converted to 5e-324 by JavaScript.
            //This situation can be ignored
            double doubleValue;
            try {
                doubleValue = decimal.doubleValue();
            } catch (Exception ex) {
                return false;
            }
            jsSupport = decimal.compareTo(BigDecimal.valueOf(doubleValue)) == 0;
        }
        return jsSupport;
    }

Please indicate you've done the following:

• Made sure tests are passing and test coverage is added if needed.
• Made sure commit message follow the rule of Conventional Commits specification.
• Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

[wenshao]

这个没解决Double输出的问题吧

[rowstop]

这个没解决Double输出的问题吧

double 和 javascript 的 Number 范围相似，只有在±Double.MIN_VALUE时会被转为±5e-324，这种情况可以忽略了，可以认为 Double 不需要额外处理

[rowstop]