(chore): Allow CodeRabbit to apply not-meet-criteria label

* Remove the instruction to extract the installer rather than running it.

Author: z-Fng

.coderabbit.yaml

@@ -28,6 +28,11 @@ reviews:
       instructions: |
         If this is a NEWLY ADDED manifest file (not a modified or renamed file) and there is no linked GitHub issue in the description or PR body,
         apply the `package-request-needed` label to indicate that the contributor needs to create a package request issue and link it in the description or PR body.
+    - label: not-meet-criteria
+      instructions: |
+        If this is a NEWLY ADDED manifest file (not a modified or renamed file) and this package does not meet the acceptance criteria for new package
+        requests (reasonably well-known and widely used, stable release available, English interface/documentation), apply the `not-meet-criteria` label
+        to indicate that this package will not be accepted.
   path_instructions:
     - path: "**"
       instructions: |
@@ -44,7 +49,6 @@ reviews:
             - Check the `description` field or the PR body for a linked GitHub issue (e.g., #123 (must be a valid issue number) or an issue URL).
               If missing, you should warn the contributor to create a package request issue and link it in the description or PR body.
             - Ensure contributor knows the acceptance criteria for new package requests.
-            - Ensure contributors understand how to extract the installer rather than running it, as this is the core concept of Scoop.
           - Acceptance criteria for new package requests:
             - Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars).
             - A stable release available (not in pre-release or alpha stage).