"diagnostics" command?

### What is the problem you're trying to solve

Users opening tickets may or may not provide some level of detail about their install, version, configuration.
Regularly, we have to ask them for more to be able to pinpoint reported issues.
Worse, they quite often copy it un-formated, or with manual edits, etc.

This is cumbersome, copy pasta error prone, incomplete, slow / back and forth type of process, leading to several days going by on undiagnosed issues just trying to collect minimal information.

### Describe the solution you'd like

Suggesting we introduce some form of a "data collect", or "bug report" command.

`nerdctl diagnostics -f report.tag.gz` ? (exact UX to be discussed)

Such a command could collect:
- info, version and config files for all main components
- (optionally) perform some networking testing (possibly with a flag `--analyze-registry XYZ`)
- (optionally) perform a set of host tests and verifications (collect specific environment variable, some `which`, sysctl dump, systemctl verifications)

... then either it would open a github ticket with all of that, or bundle it into a tar that the user can then upload manually to a github issue.

### Additional context

Details would have to be figured out and a proper proposal put forward, but interested in what we think about the general idea first.