Some IPFS repos incorrectly use v1

[guseggert]

Checklist

• My issue is specific & actionable.
• I am not suggesting a protocol enhancement.
• I have searched on the issue tracker for my issue.

Description

Some IPFS repos such as https://github.com/ipfs/go-ipfs-blockstore have released a v1, but we actually don't intend to follow idiomatic semver on those, because we intent to release breaking minor version releases to avoid a v2 bump and then the subsequent import path change. This indicates that they are not really v1, but a v0 fork.

So we need to:

• Identify all the repos incorrectly released as v1
• Add a warning at the top of each repo's README describing that it doesn't follow standard semver (minor version v1 releases can still be breaking)
• Prioritize them for consolidation as part of Consolidate IPFS Repositories #8543