Make zpool status dedup table support raw bytes -p output

[Adi-Goll]

Check if -p flag is enabled, and if so print dedup table with raw bytes. Restructure the logic in zutil_pool to check if -p flag is enabled before making calls to zfs_nicenum_format(). Other files changed update the call to/header declaration of dump_ddt_stat() to include a new variable: boolean_t parsable, indicating whether or not -p was used.

Some minor changes were made to the printing of the DDT, to ensure that when the raw bytes were printed and not truncated, there was enough space to make the output legible. This is not dynamic though, and is probably a temporary solution, but it is preferable to the previous state.

This PR also includes updates to the ABI files because the function header for zpool_dump_ddt() was modified to include a new parameter which indicates if the -p flag was used.

Fixes #11626

How Has This Been Tested?

Before this PR, when -p wasn't supported (equivalent of running the command with just -D):

$ sudo zpool status -D tank
  pool: tank
 state: ONLINE
config:

	NAME             STATE     READ WRITE CKSUM
	tank             ONLINE       0     0     0
	  /tmp/disk.img  ONLINE       0     0     0

errors: No known data errors

 dedup: DDT entries 1, size 3K on disk, 8K in core

bucket              allocated                       referenced
______   ______________________________   ______________________________
refcnt   blocks   LSIZE   PSIZE   DSIZE   blocks   LSIZE   PSIZE   DSIZE
------   ------   -----   -----   -----   ------   -----   -----   -----
    2K        1    128K    128K    128K    3.12K    400M    400M    400M
 Total        1    128K    128K    128K    3.12K    400M    400M    400M

After this PR:

$ sudo zpool status -D -p tank
  pool: tank
 state: ONLINE
config:

	NAME             STATE     READ WRITE CKSUM
	tank             ONLINE       0     0     0
	  /tmp/disk.img  ONLINE       0     0     0

errors: No known data errors

 dedup: DDT entries 1, size 3072 on disk, 8192 in core

bucket              allocated                            referenced
______   ______________________________        ______________________________
refcnt   blocks   LSIZE    PSIZE    DSIZE      blocks   LSIZE     PSIZE        DSIZE
------   ------   -----    -----    -----      ------   -----     -----        -----
  2048        1   131072   131072   131072     3200   419430400   419430400   419430400
 Total        1   131072   131072   131072     3200   419430400   419430400   419430400

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Quality assurance (non-breaking change which makes the code more robust against bugs)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

[Adi-Goll]

@amotin @behlendorf No worries if there are more pressing reviews going on right now, but I just wanted to follow up on this.

[Adi-Goll]

it may still be preferrable to do dump_opt['P'] > 0 here but I'm not sure. The value for literal seems to correspond to cb.cb_literal, which is set to B_TRUE when checking for a p option being enabled, on line 11250 of this file, so this seems to be correct from what I see but let me know if you have thoughts!

[amotin]

I would prefer to not bloat the code, but introduce two variables with formats.

[amotin]

I already dislike it...