IPNS Support

[lidel]

Filling this as a placeholder based on prior issue from ipfs-shipyard/ipfs-github-action#4

Some initial notes / ideas:

• IPNS record as opt-in feature
  • CI prodiuces signed record, and then that record can be published to N places + attached as job run artifact (enabling other cron-like job to republish).
• UX: private key as CI secret
  • can be exported via ipfs key export -f pem-pkcs8-cleartext)
  • action could create a signed IPNS record if IPNS key secret is present
    • ipfs name publish --offline + curl http://127.0.0.1:8080/ipns/name?format=ipns-record -o name.ipns-record
• UX: multiple record re-publishers (just like we have multiple pin targets for CID)
  • These should be explicit opt-in, with docs requiring user to understand the need of periodic re-publishing via GithubAction cron-like trigger
    • require / limit IPNS publishing to workflows triggered by schedule: cron ?
  • publisher ideas
    • HTTP PUT to delegated-ipfs.dev/routing/v1/ipns/{name}?
    • Amino DHT PUT – in theory PUT of signed record to 20 peers could work from Github action just fine