Fix component owners workflow permissions

[jsoref]

Description

The component owners workflow fails miserably in forks with restricted permissions because it's misconfigured:

• Improve error handling for missing issues: write/pull-requests: write dyladan/component-owners#21

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

The official documentation for the action has been consulted:
https://github.com/dyladan/component-owners/blob/58bd86e9814d23f1525d0a970682cead459fa783/README.md?plain=1#L54-L57

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[emdneto]

I'm curious why do you need that this job run on forks?

[jsoref]

I mostly want to not get ❌ when I test things. You're free to instead use an if: github.repository == ... test instead.

But, from a different perspective, the only reason this works in the main repository is because your repository/organization's permissions are lax instead of restrictive and when that's fixed and it should be fixed, this workflow will break for the main repository just as it did in my fork (which happens to be restrictive).

[emdneto]

I mostly want to not get ❌ when I test things. You're free to instead use an if: github.repository == ... test instead.

But, from a different perspective, the only reason this works in the main repository is because your repository/organization's permissions are lax instead of restrictive and when that's fixed and it should be fixed, this workflow will break for the main repository just as it did in my fork (which happens to be restrictive).

I understand your concern. It makes sense to me from the security perspective