[New Workflow] Bot to automatically reply to new issues (#2684)

* Add Issue Commenter to repo

* Update .github/issue-comment.md

Co-authored-by: BethanyG <BethanyG@users.noreply.github.com>

* Oui Oui Automation

Co-authored-by: BethanyG <BethanyG@users.noreply.github.com>

.github/issue-comment.md

@@ -0,0 +1,35 @@
+🤖   🤖
+
+Hi! 👋🏽 👋  Welcome to the Exercism Python Repo!
+
+Thank you for opening an issue! 🐍  🌈  ✨
+
+<br>
+
+-   &nbsp;   If you are **requesting support**, we will be along shortly to help. (*generally within* **72 hours,** *often more quickly*).  
+-  &nbsp;   **Found a problem** with tests, exercises or something else?? &nbsp;🎉  
+&nbsp;&nbsp;We'll take a look as soon as we can & identify what work is needed to fix it. *(generally within* **72 hours**).
+
+​		&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;If you'd also like to make a PR to **fix** the issue after discussing it,  
+&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;_We &nbsp;💙 &nbsp;PRs that follow our [Exercsim](https://exercism.org/docs/building) & [Track](https://github.com/exercism/python/blob/main/CONTRIBUTING.md) contributing guidelines!_
+
+-  &nbsp; Here because of an obvious (*and* **small** *set of*) spelling, grammar, or punctuation issues with **one** exercise,  
+&nbsp; concept, or Python document?? 🌟  `Please feel free to submit a PR, linking to this issue.` 🎉
+
+​		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ❗ Please **do not**  run checks on the whole repo & submit a bunch of PRs.  
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; This creates longer review cycles & exhausts reviewers energy & time.  
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; It may also conflict with ongoing changes from other contributors.  
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; For anything complicated or ambiguous, **let's discuss things**  --  we will likely welcome a PR from you.
+
+​		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ❗ Please keep in mind that inserting only blank lines, making a closing bracket drop to the next line, changing a word  
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;to a synonym without obvious reason, adding trailing space that's not a[ EOL](https://en.wikipedia.org/wiki/Newline) for the very end of text files,  
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and other "changes just to change things"  are **not** considered helpful, and will likely be closed by reviewers.
+
+<br>
+
+💛 &nbsp;💙 &nbsp;_While you are here..._ If you decide to help out with other [open issues](https://github.com/exercism/python/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22), you have our **gratitude** 🙌 🙌🏽.  
+Anything tagged with `[help wanted]` and without `[Claimed]` is up for grabs.  
+Comment on the issue and we will reserve it for you.  🌈  ✨
+
+_Here to suggest a feature or new exercise??_ **Hooray!** 🎉 &nbsp; Please keep in mind [_Chesterton's Fence_](https://github.com/exercism/docs/blob/main/community/good-member/chestertons-fence.md).  
+_Thoughtful suggestions will likely result faster & more enthusiastic responses from maintainers._

.github/workflows/issue-commenter.yml

@@ -0,0 +1,24 @@
+name: "Issue Commenter"
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  comment-on-new-issue:
+    runs-on: ubuntu-latest
+    name: Comments for every NEW issue.
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2.3.4
+
+      - name: Read issue-comment.md
+        id: issue-comment
+        uses: juliangruber/read-file-action@v1
+        with:
+          path: .github/issue-comment.md
+
+      - name: Base comment
+        uses: jd-0001/gh-action-comment-on-new-issue@v2.0.3
+        with:
+          message: "${{ steps.issue-comment.outputs.content }}"
+          ignore-label: ":anger: prickle"