Update validate plugin entry to account for publishing on behalf of orgs

[dvargas92495]

This change should allow plugin authors to publish plugins on behalf of their GitHub organization

[lishid]

Hmm according to the github docs, it seems to care whether the requester is the org member:
https://docs.github.com/en/rest/orgs/members?apiVersion=2022-11-28#check-organization-membership-for-a-user

Seems like it returns 302 if the requester isn't and 204 if both the requester and the username passed in is a member. Does anyone know how octokit handles the differentiation between 302 and 204?

[dvargas92495]

302s seem to just return the data, which aligns with the current then => true, catch => false logic

https://github.com/octokit/request.js/blob/master/src/fetch-wrapper.ts#L69-L118

[dvargas92495]

I just did

.checkMembershipForUser({
  org: "obsidian-community",
  username: "joethei",
})

and it actually returned a 204 locally, despite me not being in the obsidian-community org. In any case, I believe the Promise should resolve

I could also rebase this branch to the branch with my plugin PR to see if the action works as intended

[lishid]

Ok! Let's merge and see. Thank you for the contribution ❤️

[dvargas92495]

Seems to have worked!

#1342