FIx github auth for all the tooling about release

[mattymo]

What would you like to see improved? Open a browser automatically to https://github.com/settings/tokens if there is no token set?
If it's set and doesn't work, advise the user to ensure there is a token created the current set of information?

This process can't be automated internally without the user actually logging in.

[david-mcmahon]

anago and other tools run via the command-line. We need to:

• Understand the different auth mechanisms github uses
• Figure out which ones are used most commonly
• Have a check (as early in the script/process as possible) that validates all the necessary auth pathways (mostly push to various branches).
• The workflow should assume zero knowledge of github auth mechanisms and the user should simply pass the auth check or the auth check should produce a detailed set of steps to achieve the auth required for the operation with instructions on how to continue.

Related (#136), apparently --dry-run behaves differently from non-dry-run. :(

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[david-mcmahon]

Release process eventually moving to container builder, the issues raised here are no longer relevant/pressing.