Define top level Permission for ci-schedule workflow

[aditya7302]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:
Part of #5048

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[karmada-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign liangyuanpeng for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• .github/workflows/OWNERS

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

[aditya7302]

Here is the link of the CI Schedule Workflow(ci-schedule.yml) run with modified permissions :
https://github.com/aditya7302/karmada/actions/runs/9614970779

[zhzhuang-zju]

Here is the link of the CI Schedule Workflow(ci-schedule.yml) run with modified permissions : https://github.com/aditya7302/karmada/actions/runs/9614970779

@aditya7302 refer to https://github.com/aditya7302/karmada/actions/runs/9614970779/workflow, there seems be no restriction on the permissions of ci

[aditya7302]

@zhzhuang-zju I am sorry It was mistake I didn't notice I will provide you with another link of the local run with permissions added.

[aditya7302]

@zhzhuang-zju here is the updated link of the workflow run with added permissions : https://github.com/aditya7302/karmada/actions/runs/9660518622/workflow

[zhzhuang-zju]

/lgtm
cc @RainbowMango