Migrate repository from hyperledger to besu-eth organization

[jflo]

Repository Migration Plan: hyperledger/besu → besu-eth/besu

---

Phase 1: Prepare besu-eth Org (before transfer)

• Configure org-level secrets — Docker Hub creds, Artifactory tokens, SonarCloud token, etc.
• Set up SonarCloud for besu-eth organization
• Confirm pinned actions list
• Confirm branch protection rule definitions — document exact rules so they can be applied immediately after transfer
• Prepare a PR branch (on a fork or local) with all reference updates ready to merge immediately after transfer:
  • build.gradle SCM block (lines 578-588)
  • docker/Dockerfile OCI labels
  • ethereum/evmtool/src/main/docker/Dockerfile labels
  • GitHub Actions workflows with hardcoded hyperledger/besu
  • README.md badges and links
  • CONTRIBUTING.md, MAINTAINERS.md, SUPPORT.md, SECURITY.md
  • Issue/PR templates
  • release-checklist.md
  • copilot-instructions.md / .claude/ configs
  • CHANGELOG.md migration notice

Phase 2: Transfer (the brief downtime window)

• Transfer hyperledger/besu → besu-eth/besu
• Apply branch protection rules
• Merge the pre-prepared reference update PR

Phase 3: Verification

• Full CI pipeline run — all workflows pass
• Release dry-run — execute draft-release.yml end-to-end
• Verify GitHub redirects — github.com/hyperledger/besu → besu-eth/besu

Phase 4: Post-Migration

• Announce migration complete — Discord, mailing lists, blog, social media
• Update external references — Ethereum.org, Homebrew formula, third-party docs
• Monitor for broken links, CI failures, or confused users
• Communicate out brew location change when we rename the tap: brew untap hyperledger/besu && brew tap eth-besu/besu

[siladu]

Will this be a breaking change for downstream projects, e.g. consumers of evm artifacts?

[jflo]

No, no package or gav coordinates should be changed in this migration.