docs: ipfs-http-client -> kubo-rpc-client

[SgtPooki]

Tracking issue: ipfs/js-kubo-rpc-client#35
Parent issue: ipfs/js-kubo-rpc-client#6
Originating issue: #9125

This PR is intended to update the docs in ipfs/kubo so that users will be pointed to kubo-rpc-client instead of ipfs-http-client when using Javascript/TypeScript to talk to Kubo.

I noticed a lack in discussion about programmatic/api usage, so I modified more than may be expected, but I think it should be a significant improvement.

Keeping the list of http-clients up to date now involves only updating a single file in this repo. LMK if this is not desireable.

For other docs updates, follow ipfs/js-kubo-rpc-client#6

fixes ipfs/js-kubo-rpc-client#35

Things for reviewers to check:

1. Confirm I didn't miss any areas that should be updated (old mentions that should be updated that aren't yet)
2. Confirm the added information is accurate and desired
3. Confirm that the language used is aligned with maintainers' intentions

[lidel]

Thanks @SgtPooki, in general avoid "HTTP API" (as we want Gateway to be that) and use "HTTP RPC" or even "HTTP RPC at /api/v0" to remove ambiguity 🙏

[BigLep]

@SgtPooki : I see I'm a requested reviewer. I don't know if I can get to it this week. Lets incorporate Lidel's feedback and then I think we'll call that good enough.

[SgtPooki]

@lidel ping

addressed comments. need another review