Json formatting

[ReubenM]

Hope to make json output more usable:

• Trimmed strings is problematic. It makes sense to keep things tidy for visual output, but doesn't seem to serve a purpose for json output. In my use case I have dozens of gluster mounts where the mount point path is too long to be able to distinguish which mount is which after the path string is trimmed.
• Unless there is some corner-case or scenario I'm unaware of, it doesn't make much sense to quote numbers/floats as strings. When consuming json output I would have to convert them all back to numbers to make any use of them. There is one instance where the value is expressed as a percentage, but in consuming the data I would still need to convert to a numeric representation.
• Utilize bool types instead of 'y'/'n' or 1/0

[Atoptool]

I want to keep the JSON output (just like the parsable output) compatible with earlier releases. Removal of the trimming of strings would still maintain compatibility (first bullet). However, modifying strings into numbers (bullet 2) and introducing boolean values instead of y/n/1/0 (bullet 3) would introduce incompatibility.