🌱 Update GH actions to work with new release-1.6 branch

[furkatgofurov7]

What this PR does / why we need it:
Updates the GitHub Actions to work with the new release branch version

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Part of: #9094 and addresses: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#create-a-release-branch:

Update the GitHub Actions to work with the new release version.
Prior art: https://github.com/kubernetes-sigs/cluster-api/pull/9115

/area ci

[furkatgofurov7]

/hold

until release-1.6 branch is created

[sbueringer]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a501ef16e8f6400fb2eb199be982f795d1535434

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[furkatgofurov7]

/hold cancel

[furkatgofurov7]

@sbueringer do we need to update anything on release-1.6 branch now, similar to this? i.e here is what release-1.6 branch is tracking now: https://github.com/kubernetes-sigs/cluster-api/blob/release-1.6/.github/workflows/weekly-security-scan.yaml#L16

[sbueringer]

@sbueringer do we need to update anything on release-1.6 branch now, similar to this? i.e here is what release-1.6 branch is tracking now: release-1.6/.github/workflows/weekly-security-scan.yaml#L16

No, these actions are only run based on the workflow files on main