GHActions: move new 'opened' action to separate workflow (#63228)

* add new scenario to config

* make workflow run on opened issues

* revert-dont run on opened

* action for newly opened issues

* move new action config

* remove opened from commands

* change name

* Update .github/workflows/issue-opened.yml

ty!

Co-authored-by: Timur Olzhabayev <timur.olzhabayev@grafana.com>

* make comment clearer

---------

Co-authored-by: Timur Olzhabayev <timur.olzhabayev@grafana.com>

.github/commands.json

@@ -322,12 +322,5 @@
     "addToProject": {
       "url": "https://github.com/orgs/grafana/projects/78"
     }
-  },
-    {
-    "type": "author",
-    "memberOf": { "org": "grafana" },
-    "noLabels": true,
-    "addLabel": "internal",
-    "comment": " Hi there! It looks like you forgot to add any labels to this issue. We ask that members of the Grafana Org avoid filing empty issues because it slows down our triage process. Please add one or more appropriate labels. Here are some tips:\r\n\r\n- if you are making an issue, TODO, or reminder for yourself or your team, please add one descriptive label AND add the issue to your project board. :rocket:\r\n\r\n- if you are making an issue for any other reason (docs typo, you found a bug, etc), please add at least one descriptive label and the triage folks will help place it with the correct team. This really helps us move as fast as possible. :rocket:\r\n\r\nAnd please keep the `internal` tag so we can track issues created by grafanistas. Thank you! :heart:"
   }
 ]

.github/issue-opened.json

@@ -0,0 +1,9 @@
+[
+  {
+    "type": "author",
+    "memberOf": { "org": "grafana" },
+    "noLabels": true,
+    "addLabel": "internal",
+    "comment": " please add one or more appropriate labels. Here are some tips:\r\n\r\n- if you are making an issue, TODO, or reminder for yourself or your team, please add one label that best describes the product or feature area. Please also add the issue to your project board. :rocket:\r\n\r\n- if you are making an issue for any other reason (docs typo, you found a bug, etc), please add at least one label that best describes the product or feature that you are discussing (e.g. `area/alerting`, `datasource/loki`, `type/docs`, `type/bug`, etc). [Our issue triage](https://github.com/grafana/grafana/blob/main/ISSUE_TRIAGE.md#3-categorizing-an-issue) doc also provides additional guidance on labeling. :rocket:\r\n\r\n Thank you! :heart:"
+  }
+]

.github/workflows/issue-opened.yml

@@ -0,0 +1,28 @@
+name: Run commands when issues are opened
+on:
+  issues:
+    types: [opened]
+concurrency:
+  group: issue-opened-${{ github.event.issue.number }}
+jobs:
+  main:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Actions
+        uses: actions/checkout@v3
+        with:
+          repository: "grafana/grafana-github-actions"
+          path: ./actions
+          ref: main
+      - name: Install Actions
+        run: npm install --production --prefix ./actions
+      # give issue-openers a chance to add labels after submit
+      - name: Sleep for 2 minutes
+        run: sleep 2m
+        shell: bash
+      - name: Run Commands
+        uses: ./actions/commands
+        with:
+          metricsWriteAPIKey: ${{secrets.GRAFANA_MISC_STATS_API_KEY}}
+          token: ${{secrets.ISSUE_COMMANDS_TOKEN}}
+          configPath: "issue-opened"