chore: copy Issue config from nodejs.org repo

[nschonni]

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
  • This is important as most of the cases your code changes might not be correctly linted
• I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
• I have checked that the build works locally and that npm run build and npm run build-storybook work fine.
• I've covered new added functionality with unit tests if necessary.

Description

Things like doc issues shouldn't be opened on the website repo. Copying the link config from the nodejs.org repo for better instructions.

Related Issues

nodejs/nodejs.org#4752

[codecov-commenter]

Codecov Report

Merging #2580 (44294c7) into main (aa9d1ed) will not change coverage.
The diff coverage is n/a.

@@ Coverage Diff @@## main #2580 +/- ##
=======================================
Coverage 90.38% 90.38% =======================================
Files 87 87 Lines 998 998 Branches 270 270 =======================================
Hits 902 902 Misses 96 96 

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa9d1ed...44294c7. Read the comment docs.

[rodion-arr]

Probably docs template should be just renamed to something like "Learn section". I don't think it was meant to collect issues about real Node.js docs

[ovflowd]

Agreed with @rodion-arr, I'm honestly not so keen on removing the Learn section Issue template. A lot of PRs and Issues open here are for the Learn section. So removing this template kinda sucks, tbh.

[nschonni]

None of the template talks about "Learn", but wouldn't any of the issues with "Learn" be opened as a bug?

[ovflowd]

None of the template talks about "Learn", but wouldn't any of the issues with "Learn" be opened as a bug?

That's a valid point. The "bug" template is indeed enough. What about suggestions for the Learn tab? Would they fall back to "Suggestions"?

[nschonni]

https://github.com/nodejs/nodejs.dev/issues/new?assignees=&labels=enhancement&template=feature-request.yml seems to cover that case for suggesting new content

[ovflowd]

Yup, agreed! LGTM 🎉