feat: retrieve pull-secret using Red Hat SSO account

[dgolovin]

Fix #207.

This PR adds:

1. Dependency to Red Hat Account extension
2. Confirmation to allow login is requested
3. If allowed workflow goes though login in browser and retrieval of pull request using access token
4. If cancelled old workflow goes as fallback

Considered other implementation options:

1. Show Quick Picks instead of info message
2. Always do it with Red Hat Account and use manual input as backup. The problem is when login sequence is started there is not way to cancel it.

Depends on:

• feat: request confirmation to allow sign in requested from extension podman-desktop/podman-desktop#7443
• fix: Modal component is shown too high and gets out of viewport podman-desktop/podman-desktop#7466

[jeffmaury]

Works for me but I'm wondering we should enfore SSO use as manual retrieval is too complex. @slemeur WDYT ?

[slemeur]

Yes, we should enforce the use of SSO.
We could keep an option if the user wants to bring the pull secret - but that should not be the default path.

[dgolovin]

This issue podman-desktop/podman-desktop#6632 should also be fixed to make workflow better. Right now the browser just pops up and one has no idea why.

[dgolovin]

We could keep an option if the user wants to bring the pull secret - but that should not be the default path.

The option already exists - pointing to file with pull-secret in extension settings.

[jeffmaury]

Fix packaging errors

[dgolovin]

depends on podman-desktop/podman-desktop#7443.

[dgolovin]

Depends on

• fix: update macos-11 (deprecated) to macos-14 #231

[jeffmaury]

LGTM