snapcraft and other snap commands don't support a --debug for behind the scenes debugging information

I was attempting to perform a snapcraft release when the command hung. I killed it after 60s of inactivity. I then tried other snap info commands which did eventually work on 40s response times with truncated responses. I wanted to see what was up so I attempted to use a --debug on the cli in an effort to get an idea of what address/api calls it might be trying to make so I can check network routing details/etc. I was unable to get that info from the command.

I'd love to see this added as it's proven extremely helpful in my Juju cli use to be able to add a --debug and have a step by step guide on what the client is doing in an effort to help me diagnose/debug.