Update IPFS Kubo to 0.19.1

[lidel]

cc @cypt4 @bbondy @autonome

Signed Binaries: https://dist.ipfs.tech/kubo/v0.19.1/
Release Notes: https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.19.md

Some bugfixes, but there should be no impact on features exposed by Brave.

Something to consider: switch routing from auto to autoclient

0.19 adds autoclient routing mode, which will never run DHT Server, only DHT Client.

This mode aims to reduce CPU/bandwidth cost for laptop users, when user's node is publicly diallable (e.g. due to UPnP being available on the network): the implicit default auto mode will run DHT Server (if possible), autoclient won't.

Details:

• https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.19.md#addition-of-autoclient-router-type
• https://github.com/ipfs/kubo/blob/master/docs/config.md#routingtype

Should Brave do this? Depends. Did your users complain about IPFS node consuming CPU/Bandwidth since 0.18 update (#27965)?
If so, switching to autoclient may improve the situation.
If not, leave things as-is (auto is good enough).

How to force autoclient without hardcoding it in the config?

ipfa daemon supports --routing=autoclient CLI override, so Brave could add one line to from ipfs_service_impl.cc:

  args.AppendArg("daemon");
  args.AppendArg("--migrate=true");
  args.AppendArg("--enable-gc");
+ args.AppendArg("--routing=autoclient");

This will switch to Routing.Type to autoclient without touching user's config (allowing Brave to adjust this in the future).