Use organization-scoped Personal Access Tokens

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)
- This PR fixes #xyz
[ ] (If applicable) Documentation has been added / updated (for bug fixes / features).
[ ] (If applicable) Tests have been added.
[ ] This PR does not seem to break the templates.
[ ] CHANGES.rst has been updated (with summary of main changes).
- [ ] Link to issue (:issue:number) and pull request (:pull:number) has been added.

What kind of change does this PR introduce?

Updates Workflows to use Organization-scoped Personal Access Tokens

Does this PR introduce a breaking change?

No.

Other information:

The ACTIONS_VERSIONS_UPDATER_TOKEN and the BUMP_VERSION_TOKEN are Organization-scoped (Ouranosinc) personal access tokens with the following permissions for repositories xclim, xscen, miranda, figanos, and raven-hydro:

ACTIONS_VERSIONS_UPDATER_TOKEN:

Contents: Read and Write
Metadata: Read-Only
Pull Requests: Read and Write
Workflows: Read and Write

BUMP_VERSION_TOKEN:

Contents: Read and Write
Metadata: Read-Only
Pull Requests: Read and Write

Both are set to expire on January 1st, 2025. After this point, anyone with maintainer access can generate new tokens and ask the Ouranosinc admins to update the tokens so that workflows continue operating as normal.

For more information: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens

Ouranosinc / xscen