Change contents permissions from read to write on our PR Playground Preview workflow

[dkotter]

What?

Try and fix permission failures on the PR Playground Preview workflow

Why?

We are trying out a new approach to adding a Playground preview link to PRs. The initial work for this was merged in #144 (needed to be merged to test) and we're now seeing permission failures (see https://github.com/WordPress/ai/actions/runs/20372680375/job/58542974618).

How?

Updates the contents permissions from read to write to see if that fixes things

Testing Instructions

Hopefully a Playground testing link will be added to this PR. Edit: still getting the same permission error. Looks like this may need merged first before GitHub picks up the change?

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: dkotter <dkotter@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[dkotter]

@adamziel Sorry to pull you in again here but after merging in #144 to see if that would work, getting a permission error now. I was hoping changing the permissions from read to write would fix that, which is what this PR does, but still getting the same error:

Ensuring release 'ci-artifacts' exists in WordPress/ai
Creating draft release ci-artifacts in WordPress/ai
HTTP 403: Resource not accessible by integration (https://api.github.com/repos/WordPress/ai/releases)

Curious if you happen to see anything I'm missing here to make that work?

Edit: see comment below but I think we need to merge this in before GitHub will pick up the changes, same as what we ran into on #144

[dkotter]

Looking at the error logs again, I'm still seeing the permissions on contents set as read, not write:

This may be another case of needing to merge this in in order to test it