Update permissions to include admin access

[joshblack]

It seems like I have to explicitly set the permissions here to include admin 😓

[changeset-bot]

⚠️ No Changeset found

Latest commit: 954871b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull Request Overview

This PR updates the GitHub workflow permissions for the .skip-integration-checks command to include admin access in addition to write access. The change modifies a critical security parameter that controls who can override status checks via issue comments.

Key Changes:

• Modified the permissions parameter from write to 'write,admin' for the issue comment command step in the status checks workflow

[Copilot]

The permissions parameter is being changed from write to 'write,admin'. This change appears to be logically inconsistent with the comment above stating this is "critical to make sure only maintainers can run the command."

In GitHub's permission model, write permission is a lower privilege level than admin. If the goal is to restrict the command to maintainers only, adding admin to the list makes the restriction less effective, not more, since anyone with write access can already run the command.

If the intent is to restrict this to admin/maintainer access only, the permissions should be set to just 'admin' or 'maintain,admin' (excluding write). If the intent is to allow both write and admin users, then the comment should be updated to reflect this broader access level.

Suggested change

	permissions: 'write,admin'
	permissions: 'maintain,admin'