when visualizing older json records: show the result codes breakdown/details instead of just % of errors

[ldemailly]

When viewing a report in the UI (make a run, then visit http://localhost:8080/fortio/browse to see results and click one or 2 (or n) having a table of the results similar to when running the results:

# range, mid point, percentile, count
>= 0.000102018 <= 0.0002 , 0.000151009 , 8.10, 243
> 0.0002 <= 0.0003 , 0.00025 , 29.77, 650
> 0.0003 <= 0.0004 , 0.00035 , 49.70, 598
> 0.0004 <= 0.0005 , 0.00045 , 65.93, 487
> 0.0005 <= 0.0006 , 0.00055 , 78.27, 370
> 0.0006 <= 0.0007 , 0.00065 , 87.97, 291
> 0.0007 <= 0.0008 , 0.00075 , 91.90, 118
> 0.0008 <= 0.0009 , 0.00085 , 93.13, 37
> 0.0009 <= 0.001 , 0.00095 , 93.83, 21
> 0.001 <= 0.0011 , 0.00105 , 94.37, 16
> 0.0011 <= 0.0012 , 0.00115 , 94.77, 12
> 0.0012 <= 0.0014 , 0.0013 , 94.93, 5
> 0.0014 <= 0.0016 , 0.0015 , 95.17, 7
> 0.0016 <= 0.0018 , 0.0017 , 95.30, 4
> 0.0045 <= 0.005 , 0.00475 , 95.33, 1
> 0.005 <= 0.006 , 0.0055 , 98.57, 97
> 0.006 <= 0.007 , 0.0065 , 99.90, 40
> 0.007 <= 0.008 , 0.0075 , 99.93, 1
> 0.009 <= 0.01 , 0.0095 , 99.97, 1
> 0.01 <= 0.0101641 , 0.0100821 , 100.00, 1
# target 50% 0.000401848
# target 75% 0.000573514
# target 90% 0.000751695
# target 99% 0.006325
# target 99.9% 0.007
Sockets used: 70 (for perfect keepalive, would be 8)
Uniform: false, Jitter: false
Code 200 : 2938 (97.9 %)
Code 429 : 50 (1.7 %)
Code 503 : 12 (0.4 %)
Response Header Sizes : count 3000 avg 73.45 +/- 10.67 min 0 max 75 sum 220350
Response Body/Total Sizes : count 3000 avg 75.318 +/- 2.192 min 75 max 92 sum 225954
3000 calls 0.684 ms avg, 999.4 qps

or maybe just a table summary for when more than 1 are selected (with the pXX ...)