chore(github): redesign issue intake forms and routing

Overhaul the bug report form and restructure issue intake for 2.0:

- Bug report: split actual vs expected behavior, add Affected area and
  Specific tool fields for triage, replace the self-defeating required
  "latest version" checkbox with a Version field that accepts a tag,
  release, or commit (always answerable from any install), modernize
  Docker guidance to the Compose stack, add Host OS, and fix the
  previously required image-tag field that source users could not fill.
- Move feature requests to GitHub Discussions: delete the feature_request
  issue form, rename the orphaned discussion form to ideas.yml so it binds
  to the built-in Ideas category, and point config.yml there.
- Add Translation and Documentation issue forms routed to existing labels.
- Remove the roadmap-update discussion form (roadmap is private).
- Reconcile CONTRIBUTING.md, SUPPORT.md, and the published docs
  contributing guide with the new routing.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,14 @@
 blank_issues_enabled: false
 contact_links:
+  - name: Feature request or idea
+    url: https://github.com/snapotter-hq/snapotter/discussions/new?category=ideas
+    about: Suggest a new tool or improvement and let the community upvote it.
+  - name: Questions and help
+    url: https://discord.gg/hr3s7HPUsr
+    about: Ask questions, get setup help, and chat with the community.
   - name: Documentation
     url: https://docs.snapotter.com/
     about: Check the docs for setup guides, configuration, and API reference.
-  - name: Discord
-    url: https://discord.gg/hr3s7HPUsr
-    about: Ask questions, get help, and chat with the community.
   - name: Security vulnerability
     url: https://github.com/snapotter-hq/snapotter/security/advisories/new
     about: Report security issues privately through GitHub Security Advisories.