Numeral field formatter large number output invalid

[kertal]

Kibana version:
master, 7.6.0

Describe the bug:

Formatting large numbers with our default formatting template 0,0.[000], the numeral field formatter outputs other formatted numbers as expected. Eg instead of 87,595,752,619,485, it outputs 87,595,752,619,484.984

Steps to reproduce:

1. create the following index + doc

PUT telemetry
{
  "mappings": {
      "properties": {
        "long": {
          "type": "long"
        }
      }
    },
    "settings": {
      "index": {
        "number_of_replicas": "1",
        "number_of_shards": "1"
      }
    }
}

PUT telemetry/_doc/1
{
  "long": "87595752619485"
}

2. create an index pattern
3. navigate to discover, use the index pattern, expand the document. now in the table view of the document you can see the invalid output

When you change the index pattern numeral format of the field to 0 it's formatted correctly.
Browsers have issue with 64bit numbers/integer. #40183. However the number used for this demo isn't that big, but maybe an internal calculation of numeral is exceeding the limit and causes this problem?

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[smalenfant]

This doesn't seem to happen in 7.0.1.

[kertal]

@smalenfant thx for testing! 👍

[lukeelmers]

This doesn't seem to happen in 7.0.1.

I just tested this on a 7.0.1 cloud deployment, and I'm still able to reproduce the issue there. @smalenfant are you doing anything different other than what's described above to see this fixed in 7.0.1?

At any rate, this appears to be an issue in numeral that was resolved in numeral version 1.5.4 (I believe by this commit). Here's a comparison of the behavior in Numeral in 1.5.3 vs 1.5.4 demonstrating the discrepancy:

1.5.3: http://jsfiddle.net/scjr5qkm/

1.5.4: http://jsfiddle.net/s0bfcz3t/

We maintain our own fork of numeral for Kibana, and it was most recently built on 1.5.3, so cherry-picking the commit into our fork, or rebasing on top of 1.5.4 would likely resolve the issue.

[streamich]

I can verify in Kibana 7.13 we still have this problem: