GHA migration: secrets check

[enrichman]

This PR adds the steps that will use the migrated secrets, and a release.yml workflow that will be used for the releases.

The FOSSA secret with the API key is used during the CI workflow.
The Docker Hub username and password will be used during the release. At the moment we are just going to login to see that they are working fine.

This PR is needed because the branched of the CLI repo are protected, and we need PRs for them.
This is a first step "soft" PR used for the migration with no side-effects.

[enrichman]

Thanks for the review @andreas-kupries . I checked with @Anarkis and the error is expected because of the run on a different repo. Once merged we can check that the secrets are ok.
Do you think I should open the PR on a different branch? It's safe to merge on purpose.

[andreas-kupries]

Thanks for the review @andreas-kupries . I checked with @Anarkis and the error is expected because of the run on a different repo. Once merged we can check that the secrets are ok. Do you think I should open the PR on a different branch? It's safe to merge on purpose.

For my migration I actually did a test PR on a non-forked branch to check that the creds worked, and, of course the actions after also. For the FOSSA this might not be as important, as it is a code check, and not pushing anything.

[bigkevmcd]

Looks good to me!

[enrichman]

Secrets are working fine 👍

• FOSSA API key: https://github.com/rancher/cli/actions/runs/8818987612/job/24209107810
• Docker login: https://github.com/rancher/cli/actions/runs/8818997011/job/24209139489