fix(release): set provider upload repository context

[e54-bot]

Summary

• pass the GitHub repository context explicitly to provider release lookup and upload
• keep the existing target archives, checksums, and resolver-compatible asset names unchanged

Validation

• actionlint .github/workflows/provider-release.yml
• publish script Bash syntax check
• mock publish probe and baseline ablation

Fixes #176

[Teakowa]

Major — .github/workflows/provider-release.yml

This fixes the missing repository context, but keeps a 5-minute polling loop to synchronize a tag-push workflow with GitHub Release creation. That synchronization is unnecessary here: release-plz creates/publishes the GitHub Release, and GitHub provides release: types: [published] as the event for work that depends on an existing release. In the v0.1.14 evidence, the Release was already published before this workflow even started, so the retry loop only hid the missing repo context.

Trigger the provider artifact workflow from the published Release and upload directly with the explicit repository context; remove the gh release view retry loop.

[Teakowa]

#176 has been rebaselined. The current --repo patch is no longer sufficient.

Required direction: consume the release result from the shared release-plz workflow, build/publish provider binaries as downstream jobs of that same release flow, and remove the separate tag-triggered/polling lifecycle. This depends on wrightkit/.github#34 exposing the generic release outputs.