Describe the feature or problem you’d like to solve

The gh cs list command is good to get some high-level info about all of your codespaces, but is missing a few things such as what devcontainer was used, the machine display name, idle timeout, etc.

Proposed solution

This information can be fetched using the gh api command, but that requires users to know what endpoint they need to hit as well as sift through a bunch of data that isn't useful to them. We should instead add a gh cs info command that allows users to provide the name of a specific codespace or pick from a list of their codespaces to be able to get more fine-grained details about that codespace.

cc. @cli/codespaces