feat: add a logo and some basics in the README

[guseggert]

No description provided.

[BigLep]

Thanks for flushing this out further Gus. A couple of things I think would be great to add:

1. Link to docs. I assume there are go docs generated from all the modules? I'm thinking about how does someone get a sense of what tools are available to them in the go-libipfs toolbox? Clicking into each directory is hit or miss with READMEs.
2. Where someone should go to talk with the maintainers. Is it just "open an issue" or are they welcome to join a channel? (Maybe it makes sense for us to create #go-libipfs-maintainers if we don't want folks showing up to #ipfs-implementers)
3. Maybe have some expectations for each module that is added:

• Clear README
• codeowner file
• code coverage badge

[guseggert]

Thanks for flushing this out further Gus. A couple of things I think would be great to add:

1. Link to docs.  I assume there are go docs generated from all the modules?  I'm thinking about how does someone get a sense of what tools are available to them in the go-libipfs toolbox?  Clicking into each directory is hit or miss with READMEs.

2. Where someone should go to talk with the maintainers.  Is it just "open an issue" or are they welcome to join a channel?  (Maybe it makes sense for us to create #go-libipfs-maintainers if we don't want folks showing up to #ipfs-implementers)

3. Maybe have some expectations for each module that is added:


* Clear README

* codeowner file

* code coverage badge

1. I've added a godoc link to https://pkg.go.dev/github.com/ipfs/go-libipfs (the auto-generated Go docs, this is pretty standard for Go libs).

2. Good idea, the assumption is "open an issue" but Slack's a good comm channel too.

3. Also good ideas, will add.

[BigLep]

Good improvements - thanks Gus!