feat: auto-approve dry runs

[armcknight]

This would be necessary to unlock the ability to test release workflows in nightly jobs or on PR check runs. Requiring an approval for these would not scale. Uses the syntax described here to search for the appropriate label.

AFAICT the craft publish invocation will automatically pick up the dry run option from:

1. publish/src/modules/details-from-context.js

   Line 26 in 2821352

   const dry_run = context.payload.issue.labels.some((l) => l.name === "dry-run")

2. publish/.github/workflows/publish.yml

   Lines 29 to 31 in 2821352

   	- name: Parse and set inputs
   	id: inputs
   	run: node .__publish__/src/publish/inputs.js

3. publish/.github/workflows/publish.yml

   Line 99 in 2821352

   CRAFT_DRY_RUN: ${{ fromJSON(steps.inputs.outputs.result).dry_run }}

The dry-run label would be placed on the issue automatically by getsentry/action-prepare-release if getsentry/action-prepare-release#43 is merged.

Originated from getsentry/sentry-cocoa#5507

[asottile-sentry]

marking this as request changes -- I think there needs to be more thought into this and I don't think publish needs to be or should be involved at all in this

[armcknight]

Publish needs to be involved because we need to run the actual logic as closely as possible, otherwise we're not testing the thing we're using.

[armcknight]

I'm realizing now, though, that creating an issue for every single check run would be way too noisy.

[asottile-sentry]

via getsentry/action-prepare-release#43 (comment)