Resource manager items for Kubo 0.19 (the last charge)

[BigLep]

Done Criteria

These critical simplifications and UX improvements for the go-libp2p resource manager/accountant are completed:

• Resource Manager: Remove ResourceMgr.Limits configuration from Kubo and use the default libp2p JSON file for it #9603
  • This enables us to simplify Kubo config and bypass some bugs that have been experienced with the commands for altering that config
• Satisfy ResourceManager debug needs with smaller code footprint #9621
  • This enables us to simplify Kubo commands to focus on the most critical usecases. It also addresses issues like ipfs swarm limit all: returns empty "" Service and Protocol name #9577
• docs: "remote" errors from resource manager  #9653
  • Make it easier for users to understand that this is an error from the remote note.

These should happen as part of resolving the issues above, but there will be documentation updates in:

• https://github.com/ipfs/kubo/blob/master/docs/libp2p-resource-management.md
• https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmresourcemgr
• https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.19.md

Why Important

Resource manager integration into Kubo has been a thorn in maintainer and users' sides for the last few Kubo releases. We need to get over this hump so we can divert energy to other efforts.

Notes

These are previous "followup" / post launch tracking issues we've created. They are here for posterity, but this issue contains the focused list we're focused on:

• [Tracking issue] go-libp2p resource manager critical post release fixes #9442
• Resource Manager: UX and improvements. #9580

These are items that we'd ideally like to see fixed in go-libp2p, but are not blocking of this issue. If they do get done, we'll make corresponding changes in Kubo:

• rcmgr: Connections and Streams should also reserve memory libp2p/go-libp2p#2010
• rcmgr: Rename resource manager to resource accountant libp2p/go-libp2p#2011

[BigLep]

I assigned this one to you @Jorropo for 2023-02-20.
Please put me on any of the PRs, but I am non-blocking.
Thanks a lot.

[BigLep]

Removing this comment. I put it in the wrong issue.

[BigLep]

I can confirm that #9650 #9680 is the PR to watch for an attempt to resolve this issue.

[ShadowJonathan]

#9650 is this issue, I assume you mean #9680?

[BigLep]

Doh - yes - thanks- updated!