nixos/i2pd: update addressbook subscriptions

[apathyspace]

Description of changes

Follow the upstream update in the default PurpleI2P/i2pd addressbook subscriptions from 2021-01-27
Minor and trivial change

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.05 Release Notes (or backporting 21.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[curbengh]

I'm quite puzzled why upstream replaced inr.i2p with reg.i2p as default. inr.i2p is still being actively updated and includes much more domains (775 vs 108). I retain inr.i2p in #208451.

[apathyspace]

@curbengh I don't remember exactly, but there were some inconsistency at the time. I think inr.i2p didn't carry reg.i2p address or something like that. It all resulted in being unable to resolve torproject.i2p, that's basically the whole reason why I opened this PR.

As for the upstream reason, I wouldn't know, maybe it was the above, maybe having fewer domains in the root node is actually beneficial, with faster loading, or something like that.

[apathyspace]

Closed in favor of #208451