Snap package needs better error handling around unplugged `ssh-keys` interface.

[lengau]

Describe the feature or problem you’d like to solve

Although the gh snap has the ssh-keys interface, it requires manual connection. This can result in confusing error messages when connecting to a repo via SSH.

Proposed solution

• Short term: Modify the snap description to include instructions on how to manually connect the plug
• Medium term:
  • option 1: See if we can get auto-connect of the interface for the snap (not likely given historical denials: a, b. Though there is potentially a good argument that this is core functionality and would thus be unsurprising.
  • option 2: create a command wrapper for the snap that checks for an SSH URL and, if found, checks whether the plug is connected and provides a warning if not. (This could possibly even be a bash script that checks snapctl is-connected
• Long term: Assuming the snap store policy reviewers deny auto-connect, eliminate the wrapper mentioned in option 2 by providing a PR directly to the gh cli team to handle the error within a snap environment.

Additional context

It appears one of the more common bug reports the CLI team gets related to the snap package that's upsetting them is the fact that the package doesn't autoconnect the ssh-keys interface. This is creating friction and negative feelings in the community. My goal here is to work towards a positive outcome by reducing the annoyance the gh developers feel towards the snap package (which I personally prefer to their methods of distribution), providing users of the snap package with a better experience, and hopefully eventually providing sufficient positive community support to them that they change their minds about a snap package.

[casperdcl]

Could you try sudo snap install --classic gh --channel edge