[Feat]: Enforce reservations in registration and migrate off the address whitelist #204

Component

Registration

Priority

P2

Summary

Make the normal registration path honour reservations, and remove the operator mint path. A reserved name must be registrable only by its claimant; every other caller is refused that name. Part of #202.

Proposal

• In register on the registrar controller, read the reservation contract. If the label is reserved, allow only the reserved claimant to proceed, and refuse every other caller for that label.
• Remove registerReserved, or reduce it to a claimant-only path that issues only a name reserved for msg.sender. Remove onlyWhiteListedOrOwner, whiteListAddress, isWhiteListed, the WhiteListed event and the NotWhiteListedOrOwner error as the mint gate.
• Migration: define what happens to addresses currently whitelisted and to any names already issued through registerReserved. At minimum, clear the whitelist so no address keeps the unbounded mint power.
• Pricing follows the parent's open decision: normal price for the name's length, or waived for the claimant.

Acceptance criteria

• A reserved name is registrable only by its claimant; any other caller is refused that specific name.
• The address whitelist no longer grants zero-cost minting of arbitrary names.
• The migration path is defined and applied.
• Tests and the paired fork test cover a claimant registering a reserved name, a non-claimant refused, and an unreserved name registering normally.
• dotns-sdk is migrated off registerReserved and isWhiteListed, and resolves the reservation contract through the protocol registry.