docs: Add issue configuration

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: GitHub dicussions
+    url: https://github.com/empicano/aiomqtt/discussions
+    about: Ask (and answer) questions, brainstorm, and show what you've built.

.github/ISSUE_TEMPLATE/bug-report.md → .github/ISSUE_TEMPLATE/issue.md

@@ -1,15 +1,13 @@
 ---
-name: Bug report
-about: Something's not working!
-title: ''
-labels: ''
-assignees: ''
-
+name: Open an issue
+about: Report a bug or discuss a new feature
 ---
 
+<!--
 Thank you for taking the time to report an issue! We're glad to have you involved with aiomqtt.
 
 If you're filing a bug report, please consider including the following information:
 
 - The version of aiomqtt
 - A minimal self-contained code snippet that reproduces the bug (you can use `test.mosquitto.org` for a publicly available MQTT broker)
+-->

docs/introduction.md

@@ -7,5 +7,5 @@ If you're new to MQTT, we recommend reading the [HiveMQ MQTT essentials](https:/
 Thanks for being part of our community! ☀️
 
 ```{admonition} A little bit of history
-Frederik ([@frederikaalund](https://github.com/frederikaalund)) started aiomqtt to power bacteria sensors at [SBT Instruments](https://sbtinstruments.com/). One of his central ideas for the project was to use [structured concurrency](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/) principles. At first, the project was called asyncio-mqtt, until Jonathan ([@mossblaser](https://github.com/mossblaser)) graciously offered to pass along the aiomqtt name. In August 2024, Frederik passed on aiomqtt's stewardship to Felix ([@empicano](https://github.com/empicano)) due to changing priorities and to better serve the project overall.
+Frederik ([@frederikaalund](https://github.com/frederikaalund)) started aiomqtt in 2020 to power bacteria sensors at [SBT Instruments](https://sbtinstruments.com/). One of his central ideas for the project was to use [structured concurrency](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/) principles. The project was called asyncio-mqtt until 2023, when Jonathan ([@mossblaser](https://github.com/mossblaser)) graciously offered to pass along the aiomqtt name. In August 2024, Frederik passed on aiomqtt's stewardship to Felix ([@empicano](https://github.com/empicano)) due to changing priorities and to better serve the project overall.
 ```