feat: republish third-party ipns record

[tabcat]

Title

feat: republish third-party ipns record

Description

Adds the ability to keep alive an IPNS record this node did not originally
publish, plus the upkeep-policy machinery around it.

New methods on the IPNS interface:

• import(key, record): validate a record and store it locally without touching
  the network. No metadata is written, so the record is served on a GET but
  dormant until republish gives it an upkeep policy.
• republish(key, options): republish the record held locally for a key. It
  compares the local record against the network with ipnsSelector, throws
  RecordObsoleteError if a newer record is already published, otherwise
  persists the chosen upkeep policy and publishes. Best-effort on the network (a
  failing network router does not throw; use onProgress and the logs), but a
  local-store persist failure throws, since that write saves the upkeep policy.
• unpublish(key, options): stop republishing. By default it removes only the
  metadata (the record stays served until it expires); removeRecord: true also
  deletes the record.

Upkeep policy (stored per key in the metadata, default reissue):

• reissue: re-sign the record with a new sequence and validity. Needs the
  signing key, so only publish can select it.
• rebroadcast: re-put the existing record as-is. The background loop resolves
  the network's latest record first and adopts a newer one instead of pushing a
  stale copy.
• none: no upkeep.

Other changes:

• resolve skips the local store when nocache is set, and honors
  validate: false on the network path.
• The validator rejects a record whose embedded (non-identity) public key does
  not hash to its routing key.

The metadata Upkeep enum replaces the earlier refresh bool; its values are
reissue / rebroadcast / none.

Closes #877

Notes & open questions

• publish() is all-or-nothing (a single router failure fails the publish)
  while republish() is best-effort on the network.

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[gammazero]

Triage: in review

[Verity-Freedom]

сс @lidel for awareness
cc @tabcat for awareness

[hsanjuan]

Triage:

• @achingbrain will review

[tabcat]

Turning this back into a draft. There should be a way to create a new record without publishing or republishing to public routers as part of this PR.

[tabcat]

I've replaced the refresh bool field (from this pr) of the metadata protobuf for localStore with an Upkeep enum with properties republish, refresh, and none currently. The publish and republish methods now have an upkeep option with type 'republish' | 'refresh' | 'none'. 'republish' is only availabe for publish as it requires the key to sign new ttl.

[tabcat]

this still needs some work. ill convert to ready when its ready for review.

[tabcat]

I'm pretty happy with where this is at now. I've updated the description to give a pretty good idea of whats changed.

I did change the behavior of unpublish to not remove the record by default, just the metadata which sets the upkeep. I think this is the correct behavior because deleting the record loses the record sequence number. I've added an option removeRecord for the case where the user actually wants to remove the record. Not sure if this would be considered a breaking change.