README/ISSUE_TEMPLATE: point to docs and discourse

[hsanjuan]

We need to make the documentation site the place to find all the information that is currently here.
This is not a place to open issues, plus this is badly maintained and rarely updated.

Until docs-beta lands, at least mention it in some links.

@jessicaschilling what are the plans for this repo? Ideally all the info in the readme should be ingested to the docs or dropped/replaced-by-a-link because there are better places where that information is maintained.

[jessicaschilling]

@hsanjuan --

• All proposed repo fixes from the ecosystem audit can be found here, including links to longer descriptions of each.
• For convenience, direct link to item for the "do something about ipfs/ipfs" recommendation.

The short answer is that yes -- ideally this repo should (probably) still exist, but have issue-opening disabled, and the readme should really just be an evergreen set of links to the things that are being regularly updated. However, someone will need to own this -- @autonome noted his support to prioritize repo fixes overall in Q2 for the developer experience group, but we need to get those efforts into someone's actual Q2 plans who isn't already full up with work.

Regarding linking to docs beta rather than legacy docs: feel free to direct-link to docs beta. The legacy docs deprecation plan includes a step for searching all our repos for mention of such links, and amending them.

[jessicaschilling]

Thank you for triaging this! And appreciate your thoughts on longer-term plans. Let's try to get this on someone's Q2 agenda as part of some larger repo-cleanup work.