Add contents write permission to create release

[umireon]

Description

Adding the contents write permission enables the make-release job to create a release.

Motivation and Context

A GitHub Actions job has read-only permission by default and it cannot create releases without configurations.

How Has This Been Tested?

Tested on my plugin repository. https://github.com/umireon/obs-pokemon-sv-helper

Types of changes

• Tweak (non-breaking change to improve existing functionality)

Checklist:

• [ ] My code has been run through clang-format.
• [x] I have read the contributing document.
• [x] My code is not on the master branch.
• [x] The code has been tested.
• [x] All commit messages are properly formatted and commits squashed where appropriate.
• [ ] I have included updates to all appropriate documentation.

[glikely]

I don't understand why this change is necessary. I've been able to generate releases using the same template repo without this change. What specifically does adding write permission help with that doesn't work without it?

[umireon]

The default permission of GITHUB_TOKEN was recently changed from write-all to read-all and new repositories will be affected.

https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/

[glikely]

Okay, thanks for the explanation