Monitor Tab - show 95 Latency in a more readable time-unit

[nofar9792]

Which problem is this PR solving?

Resolves #892

Short description of the changes

before:

after:

[codecov]

Codecov Report

Merging #893 (c84549d) into main (fefb034) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #893   +/-   ##
=======================================
  Coverage   95.29%   95.29%           
=======================================
  Files         240      240           
  Lines        7466     7466           
  Branches     1866     1866           
=======================================
  Hits         7115     7115           
  Misses        345      345           
  Partials        6        6           

Impacted Files	Coverage Δ
...nitor/ServicesView/operationDetailsTable/index.tsx	100.00% <100.00%> (ø)
packages/jaeger-ui/src/utils/date.tsx	94.36% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fefb034...c84549d. Read the comment docs.

[yurishkuro]

Don't have a problem with this PR itself, but I am not a fan of this timeConversion function, it reduces precision more than necessary. E.g. 5900ms would be displayed as 5s - this is very misleading.

Could we fix this function to:

1. use rounding, not floor function
2. keep at least 2 significant digits
3. use lower-case units

[nofar9792]

Don't have a problem with this PR itself, but I am not a fan of this timeConversion function, it reduces precision more than necessary. E.g. 5900ms would be displayed as 5s - this is very misleading.

Could we fix this function to:

1. use rounding, not floor function
2. keep at least 2 significant digits
3. use lower-case units

lower-case units? change timeConversion or use toLowerCase only in my case?

[yurishkuro]

change timeConversion. It's weird that it mixes cases between us/ms and Sec/Hrs

[nofar9792]

change timeConversion. It's weird that it mixes cases between us/ms and Sec/Hrs

OK, it is going to affect this place too:

[nofar9792]

change timeConversion. It's weird that it mixes cases between us/ms and Sec/Hrs

done

[nofar9792]

@yurishkuro ping