feat: accept optional column argument for grid command

[Juhan280]

Description

The grid command is hardcoded to always look for name column. This pr attempts to solve this issue by accepting an additional column parameter.

Also, grid command used to return nothing instead of string if the input was an empty list, it is now resolved.

User-facing changes (Release notes)

The grid command now accepts an optional column name to display the contents of that column in a grid. One should no longer rely on the old behavior which automatically displays the name column as it is deprecated. Moreover, passing in a record as the input is also deprecated.

# before
ls | grid
{ name: test } | grid

# after
ls | grid name
[{ name: test }] | grid name

Additional notes

N/A

[fdncred]

Suggested change

	prints every item of the list in a grid layout. However, for table,
	prints every item of the list in a grid layout. However, for table or record input,

[Juhan280]

I intentionally left out record as column name doesn't work for it.

[fdncred]

why not? didn't it work in the past?

[Juhan280]

For the same reason grid doesn't accept any (string, int, bool, etc). It doesn't make sense for a scalar value to be put in a grid.

[fdncred]

so, technically, it is a breaking change because you're removing this functionality. it's just that it's probably not used. As long as a list of records and tables work, it's probably fine.

[Juhan280]

I am not removing any functionality in this pr. They are just being deprecated. But yes, when they will eventually be removed, it will be breaking.

[Juhan280]

Btw, i don't think it should be notes:breaking-changes, it just deprecates old behavior and introduces new behavior.

Also [] | grid now returning empty string instead of nothing is a bug fix.

[fdncred]

Thanks