deprecate all types and stub them to Kubo

[Jorropo]

The merge strategy here is:

1. merge client/rpc: rename package name to match rpc and edit migration story kubo#9908
2. release Kubo v0.21.0-rc1
3. fixup this PR to depend on Kubo v0.21.0-rc1
4. merge this PR
5. (blocked) release Kubo v0.21.0
6. make and merge a new PR updating this repo to Kubo v0.21.0
7. archive this repo
8. go through issue and PRs

[Jorropo]

# summary
Suggested version: v0.6.1

Seems wrong DhtAPI.Put's signature changed to allow for the allow-offline option.

[BigLep]

Thanks @Jorropo . You're plan looks good to me.

[github-actions]

Suggested version: v0.7.0

Comparing to: v0.6.0 (diff)

Changes in go.mod file(s):

(empty)

gorelease says:

# summary
Suggested version: v0.6.1

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.