chore: release v1.5.0

[lidel]

This PR is bare minimum to be able to bump dependencies with various upstream bugfixes:

• go-libp2p 0.36.1
• boxo 0.22.0

[lidel]

Old rainbow had this noopPeerLogger implementation and i had to start returning a bool after updating boxo here.

Seems that hardcoding false here causes panic in
https://github.com/ipfs/boxo/blob/v0.22.0/bitswap/server/internal/decision/engine.go#L876
panic: runtime error: index out of range [0] with length 0
go test log here

[lidel]

Removed noopPeerLedger.

Rationale:

• After looking at things bit deeper I realized WithPeerBlockRequestFilter is enough and custom PeerLedger does not help us with anything, and after overflow fixes in boxo 0.22 only causes problems (because we do want PeerLedger that correctly tracks wants that are not filtered by WithPeerBlockRequestFilter).
• Low risk since RAINBOW_SEED_PEERING is false by default, and it is marked as experimental feature (that we decided to not use in our infra).

[github-actions]

Suggested version: 1.5.0

Comparing to: v1.4.0 (diff)

Changes in configuration file(s):

diff --git a/go.mod b/go.mod
index 58381d7..aa40d01 100644
--- a/go.mod
+++ b/go.mod
@@ -20,6 +20,7 @@ require (
 	github.com/ipfs/go-log/v2 v2.5.1
 	github.com/ipfs/go-metrics-interface v0.0.1
 	github.com/ipfs/go-metrics-prometheus v0.0.2
+	github.com/ipfs/go-test v0.0.2
 	github.com/ipfs/go-unixfsnode v1.9.0
 	github.com/ipld/go-codec-dagpb v1.6.0
 	github.com/libp2p/go-libp2p v0.35.1

gorelease says:

# diagnostics
required module github.com/microcosm-cc/[email protected] retracted by module author: Retract older versions as only latest is to be depended upon

# summary
Suggested version: v1.5.0

gocompat says:

HEAD is now at 0a58582 chore: release v1.4.0 (#153)
Previous HEAD position was 0a58582 chore: release v1.4.0 (#153)
Switched to branch 'main'
Your branch is up to date with 'origin/main'.

Cutting a Release (and modifying non-markdown files)

This PR is modifying both version.json and non-markdown files.
The Release Checker is not able to analyse files that are not checked in to main. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.