Refactor publicAccessControl

[sshivaditya2019]

I realize that contributors cant add labels unless there is an issue template that allows them to create an issue and select labels when creating issues, but this is an unusual scenario that projects need to go out of their way for.¹²³⁴

Remove all references to publicAccessControl.setLabel
Refactor publicAccessControl to only be a boolean called: fundContributorClosedIssue, default is false.⁵
https://www.github.com/ubiquity-os-marketplace/assistive-pricing/blob/9984131a66eb9167dd0f60147a99e41ae382c43b/src/types/plugin-input.ts#L23-L29

Note
The reason why fundContributorClosedIssue exists is because if:

an outside party files an issue
we fund it
self assign
Then they can mark the issue closed as completed using the GitHub UI (because they created the issue) which makes an easy attack vector.

Footnotes

1. ⚠ 79% possible duplicate - Feature Request: Dark Mode for UI ↩

2. ⚠ 79% possible duplicate - Feature Request: Dark Mode for UI ↩

3. ⚠ 78% possible duplicate - Issue with Account Access ↩

4. ⚠ 78% possible duplicate - Data Upload Takes Too Long ↩

5. ⚠ 78% possible duplicate - File upload fails always ↩

[test-app-ubo]

Note

The following contributors may be suitable for this task:

gentlementlegen

76% Match ubiquity-os-marketplace/command-start-stop#62
75% Match ubiquity-os/plugins-wishlist#6
75% Match ubiquity-os-marketplace/text-conversation-rewards#207

devpanther

76% Match ubiquity/ubiquibot#288

whilefoo

76% Match ubiquity-os-marketplace/daemon-pricing#45