[Feat]: Read the network TLD from the registry in tests instead of a literal

Component

Other

Priority

P2

Summary

The test suite hardcodes the TLD as the literal .dot in roughly 36 places, for example string.concat(label, ".dot"). The TLD is per network and read live from the protocol registry, and the fixture already exposes it through protocolRegistry.tld(), derived from the single TLD_LABEL constant in BaseDotns. The literals drift from the configured TLD, so a change to TLD_LABEL would not flow through these assertions.

Proposal

• Replace string.concat(label, ".dot") and similar literals with string.concat(label, protocolRegistry.tld()).
• Keep TLD_LABEL as the single value the fixture initialises the registry with, so every derivation follows from one place.

Acceptance criteria

• No test hardcodes the TLD as a literal; full names derive from protocolRegistry.tld().
• Changing TLD_LABEL flows through every affected assertion with no other edits.

Search the test suite for hardcoded .dot literals such as string.concat(label, ".dot"), then inspect how protocolRegistry.tld() is exposed and initialized from TLD_LABEL in BaseDotns. Replace the affected literals so full names derive from the registry, and verify that changing TLD_LABEL updates every assertion without other edits.