chore: grant write permission for create-release-branch workflow

[honcao]

Reason for Change:

Issue Fixed:

Credit Where Due:

Does this change contain code from or inspired by another project?

• [X] No
• [ ] Yes

If "Yes," did you notify that project's maintainers and provide attribution?

• [ ] No
• [ ] Yes

Requirements:

• [X] uses conventional commit messages
• [ ] includes documentation
• [ ] adds unit tests
• [ ] tested upgrade from previous version

Notes:

[christinalau0]

@honcao from documentation: "Don’t use write-all as your permissions block as it opens the permissions on all scopes and you will make DSR very sad as well as get your workflow auto-disabled." https://docs.opensource.microsoft.com/github/apps/permission-changes/

Would contents: write be enough to create a new branch?