fix publish-to-bcr workflow

[mmorel-35]

Fixes #3856

Changes

Provide a registry_fork field, see https://github.com/bazel-contrib/publish-to-bcr/tree/main?tab=readme-ov-file#2-reference-the-reusable-workflow-in-your-publish-job

will require a open-telemetry/bazel-central-registry fork

For significant contributions please make sure you have completed the following items:

• CHANGELOG.md updated for non-trivial changes
• Unit tests have been added
• Changes in public API reviewed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.99%. Comparing base (75b8a2f) to head (f171a65).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3869   +/-   ##
=======================================
  Coverage   89.99%   89.99%           
=======================================
  Files         225      225           
  Lines        7170     7170           
=======================================
  Hits         6452     6452           
  Misses        718      718           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[marcalff]

Thanks for the fix.

About:

# Allow manual triggering for testing and recovery

is there a way for a maintainer to provide a custom input tag to use a different bcr fork?

Using https://github.com/marcalff/bazel-central-registry myself, I think anyone should be able to provide their own repo when using a manual workflow.