Replace standalone side-effect expression with explicit void operator

[Copilot]

Addresses review feedback on PR #324 regarding a standalone expression that relies on getter side effects.

Changes

• Replaced ma.bytes; with void ma.bytes; in parseLocationMultiaddr() to make the intentional side effect explicit
• Improved comment clarity to explain cache population necessity

Context

The ma.bytes getter populates an internal cache required for getComponents() to work correctly. The previous code used a standalone expression:

// Before
ma.bytes; // ensure bytes are populated

// After  
// Force cache population of bytes property to ensure getComponents() works correctly
void ma.bytes;

The void operator makes the intent unambiguous and prevents linters from flagging it as an unused expression.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.