lsblk: differentiate between infos[] and columns[]

Signed-off-by: Karel Zak <kzak@redhat.com>
lsblk: check number of used columns

The current code does not check size of the columns[] array when add
the next on command line specified column. We check the array size for
"-o <columns>" but not for another options.

Old version:

   $ for x in $(seq 0 100); do echo "-t"; done | xargs lsblk
   xargs: lsblk: terminated by signal 11

new version:

  $ for x in $(seq 0 100); do echo "-t"; done | xargs lsblk
  lsblk: too many columns specified, the limit is 83 columns.

Signed-off-by: Karel Zak <kzak@redhat.com>
lslocks: clean up columns[] usage

Signed-off-by: Karel Zak <kzak@redhat.com>
findmnt: more robust usage of columns[]

For more details see commit dcc8dbdc8137cb3da5100158639b565565b89875.

Signed-off-by: Karel Zak <kzak@redhat.com>
wdctl: clean up columns[] usage

Signed-off-by: Karel Zak <kzak@redhat.com>
lslogins: more robust usage of columns[]

For more details see commit dcc8dbdc8137cb3da5100158639b565565b89875.

Signed-off-by: Karel Zak <kzak@redhat.com>
losetup: clean up columns[] usage

Signed-off-by: Karel Zak <kzak@redhat.com>
swapon: clean up columns[] usage

Signed-off-by: Karel Zak <kzak@redhat.com>
prlimit: clean up columns[] usage

Signed-off-by: Karel Zak <kzak@redhat.com>