rename movementlabsxyz -> movement-network

[Primata]

Description

Renames the GitHub org reference movementlabsxyz → movement-network across the
repository, following the org rename. 33 occurrences in 19 files:

• CI / release automation — reusable-workflow refs
  (movement-network/aptos-core/.github/actions/build-{binary,container}@m1), the
  IMAGE_NAMESPACE/image_name values for the aptos-node, aptos-debugger and
  aptos-faucet-service GHCR images, the Justfile build/push targets, and the
  release-existence probe in scripts/cli/build_cli_release.sh.
• Claude PR audit workflow — REVIEWER_REPO: movement-network/claude-pr-reviewer
  (REVIEWER_REF: v1 unchanged).
• Code constants — the framework git URL used by aptos move init
  (crates/aptos/src/move_tool/mod.rs) and the shallow-clone URL used for merge-base
  metadata in devtools/aptos-cargo-cli/src/common.rs.
• Move manifests — AptosFramework git dependency URLs in the
  movement-migration/* packages.
• Release metadata — source_code_url / discussion_url in
  aptos-move/aptos-release-builder/data/release.yaml and the generated
  disable_concurrent_fungible_balance.json.
• Docs / comments — homebrew README, docker/aptos-debugger/README.md, and the
  PR link in the pipelined_block.rs regression comment.

No functional or behavioral change. GitHub keeps redirects for renamed orgs, so nothing
was broken before this; the change makes the references match reality.

Incidental formatter noise is included in the same commit (no logic touched):
crates/aptos/src/move_tool/mod.rs struct literals reflowed by rustfmt,
scripts/cli/build_cli_release.sh re-indented to tabs, build-versions.yaml quote
style plus trailing-whitespace cleanup, and homebrew README list indentation.

How Has This Been Tested?

• grep -ril movementlabsxyz . returns zero hits repo-wide.
• Reviewed every hunk by hand to confirm each change is either the org rename or
  formatter-only.
• CI on this PR exercises the renamed reusable workflows / GHCR namespace; the
  container publish paths must be confirmed green before merge.

Key Areas to Review

• .github/workflows/build-versions.yaml — the uses: refs and IMAGE_NAMESPACE
  must resolve under the new org and the GH token must still have push rights to
  ghcr.io/movement-network/*. This is the one place a wrong value fails only at
  release time.
• .github/workflows/claude-audit-pr.yml — movement-network/claude-pr-reviewer
  must exist with tag v1.
• crates/aptos/src/move_tool/mod.rs / movement-migration/*/Move.toml — these URLs
  end up in user-facing generated manifests and in migration packages; a bad URL breaks
  aptos move init / package resolution for downstream users.
• Formatter churn — if you'd rather keep the rename diff surgical, say so and I'll
  split the reformatting into a separate commit.

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (CI/CD workflows, container image namespace, release metadata, migration Move packages)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}