[saket0187]

This PR adds the feature requested in #7437

• Added brief documentation updates.
• Added Output format options

There is currently no test suite available for t.list. I wasn't sure if a new test file (e.g., using pytest) should be introduced in this PR, so I plan to address testing in a future PR instead. If there are any reference implementations or guidelines for using pytest within the temporal modules, please let me know!

[echoix]

If you're adding tests for more than what you added: a new PR to merge first (so then your PR changing the behaviour can catch if breaking something existing).

If you're adding tests only for what you're adding (and it cannot impact existing code), then tests in this PR is welcome.

@petrasovaa are pytest tests in temporal now behaving correctly? I remember seeing one of your PRs addressing something on the subject

[petrasovaa]

@petrasovaa are pytest tests in temporal now behaving correctly? I remember seeing one of your PRs addressing something on the subject

Running t.info should be fine, I think the problem is more with running the temporal API directly. So yes, let's do a PR with pytest first.

[petrasovaa]

The JSON output should just be a flat array of datasets, not structured under mapsets, similarly the "line" format should be all in one line. We could add mapset option similar to g.list to filter by it, but out of scope of this PR.
Also, the stderr info messages should be used only for plain format (interactive use).
The JSON should likely use columns=all by default unless specified. With other tools we have usually included all information in the JSON output.

[petrasovaa]

Looks good!