test: basic routing interface test

[hacdias]

Adds missing tests from #91. The tests depend on other APIs. Feel free to suggest improvements to depend less on others. PR in Kubo with this commit: ipfs/kubo#9628

---

Also, while doing this, I realised that the interface we added for the routing API might not be the most intuitive: see #104.

[Jorropo]

LGTM

[Jorropo]

Would be nice if we would try to fetch the thing we stored, this would catch silent failure, with the current setup that would not work since you don't know if this was stored by the original ipns publish or the second put.

[hacdias]

@Jorropo i can do that too. I didn't do it initially for illustration purposes since I didn't want to be adding random things.

[hacdias]

@Jorropo actually, I think there must be some kind of internal verification afterwards. If you do ipfs routing put and then get, you won't get the same result. For example, if you put random data on your self key, you'll just get the latest ipns key. So I think there's some DHT verification somewhere to avoid invalid data to getting added.

[Jorropo]

@hacdias yes https://grep.app/search?q=validator&filter[repo][0]=libp2p/go-libp2p-kad-dht

[Jorropo]

that enough to make progress on ipfs/go-ipfs-http-client#168, ty 🎉

[github-actions]

Suggested version: v0.11.0

Comparing to: v0.10.0 (diff)

Changes in go.mod file(s):

diff --git a/go.mod b/go.mod
index af97472..2688cf3 100644
--- a/go.mod
+++ b/go.mod
@@ -66,4 +66,4 @@ require (
 	lukechampine.com/blake3 v1.1.7 // indirect
 )
 
-go 1.18
+go 1.19

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: v0.11.0

gocompat says:

Your branch is up to date with 'origin/master'.

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 master. 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.