docs: add LayerZero, EigenLayer, and Hyperlane target metadata

[ccai40359-wq]

Summary

• Add key contract addresses for LayerZero, EigenLayer, and Hyperlane in scout/data/targets.yaml
• Add official source links for each protocol's contract address documentation
• Keep the change focused on the target registry metadata only

Fixes #8

/claim #8

Verification

• python3 -m pytest -q — 16 passed
• Manual registry assertion: Registry.load() returns LayerZero, EigenLayer, and Hyperlane with contract entries, and each YAML entry includes source_links
• Security scan of added lines: security_findings_count 0
• Independent review: passed; no security concerns or blocking logic errors

Verified on Linux.

[abhicris]

Welcome to kcolbchain, @ccai40359-wq — glad you're here. 🌱

Here's what happens from this PR:

1. Our automated review looks for obvious issues (tests, secrets, size) within a couple of hours.
2. If it's clean and CI passes, we merge without back-and-forth.
3. If we need changes, we'll leave a specific comment — not a generic nit. Push another commit and we re-review.

While you wait:

• Run the repo's tests locally (see the repo README.md).
• Keep the PR scoped to one concern — bigger PRs land slower.
• Don't commit tokens or .env contents.

What happens after your first merge

• You're listed on https://kcolbchain.com/contributors/ (opt-out anytime via data/contributors-optout.txt).
• At 2+ merged PRs you're a Regular; at 5+ you're a Fellow — Fellows are the pool we invite first for paid research, partner-org gigs, and grant-funded work. Details: https://kcolbchain.com/docs/org-contribution-policy.html
• Looking for what to pick up next? https://kcolbchain.com/invitations/ lists open help-wanted / good-first-issue across every kcolbchain repo.

Thanks for writing the code. We're building this to last.

[Pattermesh]

Your PR was selected as the winning submission for this issue — great work! However, it now has merge conflicts with main (from other recently merged PRs). Could you please rebase against main and force-push? We'll merge as soon as the conflicts are resolved. Thank you!

[abhicris]

🤖 Audit verdict: safe

Straightforward metadata addition to YAML with official source documentation links provided for verification; no executable code, credentials, or supply-chain modifications.

Audited by the kcolbchain PR pipeline. See pipeline docs.