Precise byte counts no longer available for ‘tshark -z conv’

Summary

tshark is no longer capable of displaying raw byte counts for conversations (-z conv). This is a side-effect of #15360 human-readable numbers.

Steps to reproduce

Run tshark -qz conv,eth -r <pcap> on Ubuntu 20.04 (tshark v3.2.3) and note the raw byte counts:

                                               |       <-      | |       ->      | |     Total     |    Relative    |   Duration   |
                                               | Frames  Bytes | | Frames  Bytes | | Frames  Bytes |      Start     |              |
Sophos_16:0a:38      <-> QuantaCo_85:c1:76        371     63586     288     50018     659    113604     0.000000000       130.9257
IPv6mcast_01:00:02   <-> Universa_44:2e:2c          3       450       0         0       3       450     3.486481000        48.0019

Run the same command on Ubuntu 22.04 (tshark v3.6.2) and note the human-readable byte counts:

                                               |       <-      | |       ->      | |     Total     |    Relative    |   Duration   |
                                               | Frames  Bytes | | Frames  Bytes | | Frames  Bytes |      Start     |              |
Sophos_16:0a:38      <-> QuantaCo_85:c1:76        371 63kB          288 50kB          659 113kB         0.000000000       130.9257
IPv6mcast_01:00:02   <-> Universa_44:2e:2c          3 450bytes        0 0bytes          3 450bytes      3.486481000        48.0019

What is the current bug behavior?

Human-readable byte counts are output and there's no config option to obtain raw values.

What is the expected correct behavior?

It should be possible to output raw byte counts when precise counts are required (like capinfos -M).

Sample capture file

Any capture file with a conversation with more than 1kB.

Relevant logs and/or screenshots

N/A

Build information

Any build after #15360 human-readable numbers was committed.