track: multiformats upgrade

[achingbrain]

This issue is to track the upgrade from ipld-dag-* formats to block codecs from the multiformats module.

Why

• The ipld-dag-* are no longer maintained - development focus is now centred on multiformats and the @ipld/dag-* modules
• multiformats and @ipld-dag-* have types and docs
• Simpler story for users as there will only be one set of supported formats
• Allows use of new ipld formats like dag-jose without shims
• @ipld/dag-* modules are significantly smaller resulting in reduced bundle sizes
• Reduces maintenance burden as ipld-dag-* modules can be retired in favour of @ipld/dag-*

Repo track list

Because this is a breaking change and we do not want to block the release of bug fixes or features in the interim, these PRs will be held as drafts until #3556 is green in CI as it pulls them all together, then all will be merged and released in quick succession.

Done = ✅
In Progress = 🚧
TODO = ⛔

Status	Repo/PR	Owner
✅	js-ipfs #3556	@vmx/@achingbrain
⛔	dag-cbor-links	-
✅	ipfs/js-ipfs-bitswap#340	@achingbrain
✅	ipfs/js-ipfs-repo#313	@achingbrain
✅	ipfs/js-ipfs-repo-migrations#98	@achingbrain
✅	ipfs/js-ipfs-unixfs#116	@vmx/@achingbrain
✅	ipfs-shipyard/is-ipfs#42	@achingbrain
✅	libp2p/js-libp2p-kad-dht#220	@achingbrain
✅	libp2p/js-libp2p#948	@achingbrain
✅	multiformats/js-multiaddr#200	@achingbrain
✅	libp2p/js-peer-id#149	@achingbrain
✅	libp2p/js-libp2p-interfaces#98	@achingbrain
✅	libp2p/js-libp2p-delegated-peer-routing#46	@achingbrain
✅	libp2p/js-libp2p-delegated-content-routing#52	@achingbrain
✅	libp2p/js-libp2p-utils#18	@achingbrain

Other issues

• feat!: add CIDVersion type multiformats/js-multiformats#87
• chore(deps)!: bump multiformats from 8.0.6 to 9.0.0 ipld/js-dag-pb#17
• chore(deps)!: bump multiformats from 8.0.6 to 9.0.0 ipld/js-dag-cbor#28
• chore!: upgrade multiformats and @ipld/dag-* modules ipld/js-car#23
• chore(deps): bump multiformats from 8.0.6 to 9.0.0 ipld/js-ipld-garbage#7
• feat: support v0 identity cids multiformats/js-multiformats#91
• feat: add name and code fields to MultihashHasher interface multiformats/js-multiformats#95

Afterwards

Deprecate the following modules on npm and archive their repos:

• https://www.npmjs.com/package/ipld
• https://www.npmjs.com/package/ipld-dag-pb
• https://www.npmjs.com/package/ipld-dag-cbor
• https://www.npmjs.com/package/ipld-raw
• https://www.npmjs.com/package/ipld-git
• https://www.npmjs.com/package/ipld-ethereum
• https://www.npmjs.com/package/ipld-zcash
• https://www.npmjs.com/package/interface-ipld-format
• https://www.npmjs.com/package/protons
• https://www.npmjs.com/package/multibase
• https://www.npmjs.com/package/multihashing
• https://www.npmjs.com/package/multihashing-async
• https://www.npmjs.com/package/ipfs-block-service

[BigLep]

Thanks @achingbrain for putting this together. I set you as the assignee and put it on the maintenance board.

A couple of questions:

1. Will we be able to delete/archive some repos at the end of this? If so, can we make sure that is part of closing out this issue?
2. Will items be marked ✅ when they are merged or ready for merge? I'm wondering if we need another state or states (e.g., "in reviewer's court", "ready for merge", "merged").

[achingbrain]

1. Yes, we should be able to archive a bunch of repos - I've added some to the OP off the top of my head
2. Normally merged and released but I think here it would mean "Approved" so we can do the merges in one go when feat: upgrade to the new multiformats #3556 is green. Can add extra statuses if you think it'd be useful but in the past ⛔ 🚧 ✅ has been enough.

[achingbrain]

Shipped in ipfs-core@0.9.0 and ipfs-http-client@51.0.0