Add flag to gh api allowing disable HTTP redirect following

[andyfeller]

Describe the feature or problem you’d like to solve

Several GitHub API endpoints return URLs that GitHub CLI follows by default. This is normally okay for some, however there are use cases where users would like not to follow the redirect:

• @timrogers in Add --skip-download option to print the archive URL rather than download it andyfeller/gh-repo-export#17
• @andyfeller in Support for viewing, managing, and accessing workflow artifacts #6532

Similar to work done in #7106, it should be possible to add a flag that allows the user to disable redirect following; this is suggested to avoid breaking the default behavior up to now

Proposed solution

• GitHub API endpoints that return URLs can be used without forcing the user to download or access the resource
• Simplifies certain extensions

Additional context

Add any other context like screenshots or mockups are helpful, if applicable.

[peterramaldes]

As I understood, this already done by #7106, right?

[andyfeller]

As I understood, this already done by #7106, right?

This was something selectively done in gh repo delete, yes.

For this issues, I was thinking for a way that gh api executions that result in a URL would simply return the url rather than Go http.Client going on to request the URL itself.