[Issue] `pipeline config` and GitHub Codespaces issues

[jongio]

1. It hangs when trying to auth with GitHub at the SSH phase, I had to manually call gh auth login. I had to kill the process a few times for it to tell me I needed to gh auth login
2. It requires you to clear the GITHUB_TOKEN env var to set secrets.
3. It is only configured to run on main/master and my branch was azd. We should help the user figure out how to make that work without them guessing.
4. The azd auth flow for Codespaces requires many hoops, including using a special flag --use-device-code=False and curl in a new terminal to get it to work.
5. I couldn't figure out a way to configure a new secret in GH that could have been pulled from azd env.
6. The action fails because it isn't logged into azd properly.

I have published an internal video with these issues and shared with the team.

[weikanglim]

@jongio Will try to move out to separate issues for better tracking:

• 1 and 2 is captured separately as legitimate product regressions as #1938
• 3 is a feature ask. Maybe we should always prompt for a branch?
• Need details on 4 before acting on it. I suspect this is once again MSGraph's authorization policies that prevent us from using device-code. We can't pop-up a browser inside a browser, and AAD specifically treats "device-code" as less secure. I'm not familiar of other options. Perhaps an AAD team ask is appropriate.
• 5: Seems reasonable as a future feature ask. azd pipeline secret set? Does this end up duplicating gh functionaility?
• 6: Could be related to 4

[rajeshkamal5050]

Fixing #1938 should fix the regressions 1,2 around Codespaces <-> Pipelines.

Leaving the other asks above in Backlog for future enhancements/features.

cc @savannahostrowski @ellismg