[bricke]

Summary

• bacaro_new gains an optional second argument: a NULL-terminated array of domain strings the process publishes (e.g. {"sensors", "power", nullptr})
• At startup, a .manifest file is written alongside .pub and .rep; it is cleaned up on bacaro_destroy
• When a peer is discovered, its manifest (if present) is read and stored in PeerInfo
• DEALER socket creation and snapshot requests are skipped for peers whose declared domains don't overlap with the local subscriptions — reducing unnecessary connections at boot
• Backwards compatible: passing nullptr preserves existing behaviour exactly

Why

On a device with many processes, every subscriber used to send snapshot requests to every peer at discovery, even when there was no domain overlap. The manifest lets processes declare what they publish at startup so peers can skip those handshakes entirely.

Test plan

• All existing tests pass (ctest)
• No manifest (nullptr) behaves as before
• Overlapping subscription creates DEALER and receives snapshot
• Non-overlapping subscription skips DEALER entirely
• Hierarchical domain overlap (parent/child prefix) works correctly
• manifest_overlaps unit tests cover exact match, child, parent, empty prefix, and no-overlap cases