Run system rspec for workhorse changes

Because workhorse changes can affect how we handle requests

.gitlab/ci/rules.gitlab-ci.yml

@@ -939,6 +939,8 @@
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
+    - <<: *if-merge-request
+      changes: *workhorse-patterns
     - <<: *if-merge-request
       changes: *ci-patterns
     - <<: *if-automated-merge-request
@@ -962,6 +964,9 @@
     - <<: *if-merge-request
       changes: *core-backend-patterns
       when: never
+    - <<: *if-merge-request
+      changes: *workhorse-patterns
+      when: never
     - <<: *if-merge-request
       changes: *ci-patterns
       when: never
@@ -1131,6 +1136,8 @@
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
+    - <<: *if-merge-request
+      changes: *workhorse-patterns
     - <<: *if-merge-request
       changes: *ci-patterns
     - <<: *if-automated-merge-request
@@ -1156,6 +1163,9 @@
     - <<: *if-merge-request
       changes: *core-backend-patterns
       when: never
+    - <<: *if-merge-request
+      changes: *workhorse-patterns
+      when: never
     - <<: *if-merge-request
       changes: *ci-patterns
       when: never
@@ -1283,6 +1293,8 @@
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
+    - <<: *if-merge-request
+      changes: *workhorse-patterns
     - <<: *if-merge-request
       changes: *ci-patterns
     - <<: *if-automated-merge-request
@@ -1307,6 +1319,9 @@
     - <<: *if-merge-request
       changes: *core-backend-patterns
       when: never
+    - <<: *if-merge-request
+      changes: *workhorse-patterns
+      when: never
     - <<: *if-merge-request
       changes: *ci-patterns
       when: never