fix: improve sorting logic in renderSummary to handle NaN values

[waynexia]

Fix render logic.

Some cases (like Elasticsearch (no source, best compression)) will bring NaN values. They may break the sorting logic and generate weird illustrations.

This patch enhances NaN handling in both comparison logic and relative scale rendering.

[waynexia]

Now it can sort the NaN to the last, with the correct scale bar rendering

[rschu1ze]

@waynexia Thanks for this PR, I think it can be merged.

One question I had is why we show "NaN" at all for "Elasticsearch (no source, best compression)". I could not find "NaN" in the corresponding result .json file (and in fact I could not find "NaN" in any result .json file of any database).

[sunng87]

it seems we missed total_size for "Elasticsearch (no source, best compression)"

[rschu1ze]

It is better to correct the single incorrect JSON document (out of >60 JSON documents), than to add special handling in JavaScript. In this particular case, field total_size is affected and every benchmarked database is expected to provide some sort of total size information (i.e. NaN is not a viable value).

--> #28