Modify automated "support" message.

Make message a bit more empathetic, and give more directions about where to get help.

Also, add comment at top to help people who stumble on the YML file understand its role.

.github/workflows/support.yml

@@ -1,3 +1,8 @@
+# When a user creates an issue that is actually a support request, it should
+# be closed with a friendly comment.
+#
+# This triggers on an issue being labelled with the `support` tag.
+
 name: 'Support Requests'
 
 on:
@@ -16,12 +21,15 @@ jobs:
           github-token: ${{ github.token }}
           support-label: 'support'
           issue-comment: >
-            👋 @{issue-author}, we use the issue tracker exclusively for bug reports
-            and feature requests. However, this issue appears to be a support request.
-            Please use our [support channels](https://github.com/kivy/buildozer#support)
-            to get help with the project.
+            👋 @{issue-author},
             
-            Let us know if this comment was made in error, and we'll be happy
-            to reopen the issue.
+            Sorry to hear you are having difficulties with Kivy's Buildozer; Kivy unites a number of different technologies, so building apps can be temperamental.
+
+            We try to use GitHub issues only to track work for developers to do to fix bugs and add new features to Buildozer. This issue has been closed, because it doesn't describe a bug or new feature request for Buildozer.
+
+            There is a mailing list and a Discord channel to support Kivy users debugging their own systems, which should be able to help. They are linked in the [ReadMe](https://github.com/kivy/buildozer#support). For building Android apps, there is an unofficial [Buildozer Users' Guide](https://github.com/Android-for-Python/Android-for-Python-Users) that has a lot of useful debugging tips.
+
+            Of course, if it turns out you have stumbled over a bug in Buildozer, we do want to hear about it here. The support channels should be able to help you craft an appropriate bug report.
+          
           close-issue: true
-          lock-issue: false
+          lock-issue: false