This PR got picked up by @lidel, who created below high level description:

This updates HTTP RPC wire format to wrap binary data in multibase to fix bug entire class of bugs described in #7939

TODO

• sharness
• go-ipfs-api
• go-ipfs-http-client
• interface-go-ipfs-core (update tests to be more robust - can be done async - we just need to ensure we test with topic/payload that has \n)
• decide if we prefer to keep public API unchanged, or switch topic names to be []byte
  • descoped. does not seem to be a useful change. wire format change has limited scope, and if someone uses client library in GO or JS they only need to update to latest version, no changes in code required. if we ALSO change the programmatic API in GO and JS that forces consumers to refactor their code, which is a separate thing that we can do in the future, but no need to do now.
• decide if we are ok with js-ipfs and js-ipfs-http-client returning peerid as CIDv1 while go-ipfs uses old notation
  • descoped. peerid is opaque string identifier, API design should make no assumption beyond this fact
• interop tests from fix: multibase in pubsub http rpc interop tests interop#387
  pubsub tests in ipfs/interop need JS and GO to act the same, so we need to land:
  • js-ipfs-http-client (use new wire format) – tracked in fix(pubsub): multibase in pubsub http rpc js-ipfs#3922
  • js-ipfs (use new wire format) – tracked in fix(pubsub): multibase in pubsub http rpc js-ipfs#3922
  • fix CI failing (https://github.com/ipfs/interop/runs/3965762343?check_suite_focus=true#step:6:3446)
  • then make sure interop tests pass:
    • GO-GO
    • JS-JS
    • JS-GO
    • GO-JS
    • disable pubsub interop tests on CI
      switching to npm version with fix: disable pubsub until http rpc changes land interop#388 so other PRs and master are not impacted.
    • enable pubsub interop tests:
      merge fix: multibase in pubsub http rpc interop tests interop#387 after both GO and JS releases shipped and swich to new release

Closes #7939
Closes #8454