feat: correct context and skip issues outside of the org

[whilefoo]

Resolves #131

The issue is that start function was getting the context associated with the PR's repo but the issue was from another repo. I fixed it by creating a new context from the old context and replacing issue and repository from the API, but this feels more like a hack because the config will be from the original repo.

Another problem is that the PR's repo and issue's repo have to be in the same organization because the plugin only has installation token for the org and it doesn't have write permissions in other orgs. For example I made a PR in ubiquity-os-marketplace/text-conversation-rewards and linking to ubiquity-os/plugins-wishlist, this won't work because of the permissions.
A solution would be that we somehow move the logic so that it happens in the issue instead of the PR, but I couldn't find any webhook that would be triggered when an issue got a PR linked, cross-referenced or something similar to that so that we could trigger it based on that.

[gentlementlegen]

What about creating a new Octokit instance with the proper credentials for the other organization from this plugin? It is possible because we have the APP_ID and the APP_PRIVATE_KEY, and this technique has been used in other plugins to solve authentication issue. Maybe it would be worth having this function exposed from the SDK.

[github-actions]

Unlisted dependencies (1)

Filename	unlisted
src/handlers/user-start-stop.ts	@octokit/auth-app

[whilefoo]

Enabled support for cross-org with APP_ID and APP_PRIVATE_KEY and added tests

cross-org QA: PR and issue

[0x4007]

QA isn't 100% clear to me I left a comment on QA PR

[whilefoo]

Made another PR so the errors aren't present

[gentlementlegen]

Tested it, not sure if I did something wrong but the issues doesn't appear to be fixed:

• created a pull-request: Fork/ubiquity whilefoo/fix Meniole/command-start-stop#63
• linked to another organization: 10 mentlegen-2/project#10
• got assigned to the wrong issue: Issue 3 Meniole/command-start-stop#10

The version I used is a deployed worker created from your PR changes.

Edit: it works fine, the deployed code was not taken from the proper branch. @whilefoo Could you please fix the worker deployment script and change the checkout step to:

      - uses: actions/checkout@v4
        with:
          ref: ${{ github.event.workflow_run.head_branch || github.ref }}

so the proper code source is pulled during build?