fix(results): prefer project mappings for registered projects

[christso]

What changed

• Changed config loading so project-local .agentv/config.yaml no longer blocks global results_by_project mappings from being attached.
• Preserved fallback behavior: project-local top-level results is still used when the registered project id has no global mapping, and top-level global results remains the fallback when no project-local config exists.
• Updated Dashboard docs to describe the registered-project precedence.

Why

The non-Docker Dashboard deployment writes machine-local result repo settings to $AGENTV_HOME/config.yaml. A checked-in project-local top-level results block could previously override that machine-local project mapping, causing /api/projects/:projectId/remote/status to report the wrong clone path and auto_push: false.

Verification

• bun install
• bun test packages/core/test/evaluation/loaders/config-loader.test.ts
• bun --filter @agentv/eval build && bun --filter @agentv/core build
• bun test apps/cli/test/commands/results/serve.test.ts
• bun --filter @agentv/core typecheck
• bun --filter agentv typecheck

[cloudflare-workers-and-pages]

Deploying agentv with    Cloudflare Pages

Latest commit:	1fc5a6f
Status:	✅  Deploy successful!
Preview URL:	https://7cc46cbe.agentv.pages.dev
Branch Preview URL:	https://feature-agentv-results-by-pr.agentv.pages.dev

View logs