switch to @chainsafe/is-ip (away from @achingbrain/ip-address)

[SgtPooki]

Is there a reason why we're still using @achingbrain/ip-address, or even ip-address, when it's outdated? There seem to be better and more up to date alternatives: https://npmtrends.com/ip-vs-ip-address-vs-ipaddr.js. Though maybe they don't do everything we need them to?

One of ip-address 's dependencies, jsbn, is very stale and very underused in comparison to it's competitors: https://npmtrends.com/bignumber.js-vs-bn-vs-bn.js-vs-jsbn

There is also the native BigInt which has been around for a while: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt

We only seem to have a very small surface area for each here:

• ip-address - https://github.com/search?q=repo%3Alibp2p%2Fjs-libp2p+ip-address&type=code
• jsbn - https://github.com/search?q=repo%3Alibp2p%2Fjs-libp2p+jsbn&type=code

I also seem to remember some concerns around node-forge being used in js-libp2p and this may be another place where we could reduce our ties to it.

---

I'm not aware of the nuances but generally if a project leaves a PR that we need (beaugunderson/ip-address#148) untouched for over a year (it's going on 2), and we still don't have a permanent place to modify code for our patched version, we should probably think about migrating, or publishing our version.

cc @achingbrain. related to ipfs/helia#73 (comment)

[SgtPooki]

w.r.t. BigInt we're using https://www.npmjs.com/package/protons, which uses BigInt as well

[achingbrain]

@achingbrain/ip-address is just ip-address with beaugunderson/ip-address#148 applied.

is there a reason why we're still using [insert module name here]

Not generally no, outside of "it works" and "it doesn't cause enough problems to bring eyeballs to it".

Since this is now starting to cause problems I think we can switch it out for @chainsafe/is-ip which we use elsewhere in the stack.