fix: direct peering data needs to be processed by the worker due to obscure node behavior

[CassOnMars]

Why is this change needed?

Peer id validation performs a check of the existence of an object key that is a symbol. When we pass this over to the gossip node worker, the structuredClone copy drops this key (and functions), which was causing a crash when using direct peers. The loss of functions would have been more pronounced in discovering this, but because the check was on the symbol first, it appeared to be a libp2p bug, until it was discovered the symbol-based key itself was being omitted per specification.

Merge Checklist

Choose all relevant options below by adding an x now or at any time before submitting for review

• PR title adheres to the conventional commits standard
• PR has a changeset
• PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
• PR includes documentation if necessary.

---

PR-Codex overview

This PR focuses on updating the direct peering data handling in the hubble and gossipNodeWorker modules.

Detailed summary

• Updated directPeers type to string[] in hubble.ts and gossipNode.ts
• Modified direct peer address processing logic in cli.ts and gossipNodeWorker.ts
• Added parseAddress function import in gossipNodeWorker.ts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

🦋 Changeset detected

Latest commit: e79ab6a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@farcaster/hubble	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hub-monorepo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 10, 2024 9:05pm