fix: default to bitswap-client-only

[lidel]

@aschmahmann as discussed, this restores bitswap setup we had in v1.0.0 where only the client is initialized by default.

If this looks ok, we can ship this as v1.2.2 and deploy to our infra.

[lidel]

💭 I wonder if doing this (making NotifyNewBlocks no-op) has impact on the client. Just to be sure, we do not do this by default.

[hacdias]

This was was already a question I had when we introduced the peering, so it seems that it indeed creates more traffic. The change makes sense then.

[github-actions]

Suggested version: v1.2.2

Comparing to: v1.2.1 (diff)

Changes in go.mod file(s):

(empty)

gorelease says:

# diagnostics
required module github.com/microcosm-cc/bluemonday@v1.0.1 retracted by module author: Retract older versions as only latest is to be depended upon

# summary
Suggested version: v1.2.2

gocompat says:

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.