Switch to PR-based benchmark pipeline defined in ES repo

.buildkite/pipelines/pull-request/performance-benchmark.yml

@@ -0,0 +1,3 @@
+steps:
+  - label: ":pipeline: TODO"
+    command: echo TODO

.buildkite/pull-requests.json

@@ -18,7 +18,7 @@
     },
     {
       "enabled": true,
-      "pipeline_slug": "elasticsearch-performance-esbench-pr",
+      "pipeline_slug": "elasticsearch-pull-request-performance-benchmark",
       "allow_org_users": true,
       "allowed_repo_permissions": [
         "admin",

catalog-info.yaml

@@ -301,3 +301,39 @@ spec:
         Daily:
           branch: main
           cronline: "@daily"
+---
+# yaml-language-server: $schema=https://gist.githubusercontent.com/elasticmachine/988b80dae436cafea07d9a4a460a011d/raw/e57ee3bed7a6f73077a3f55a38e76e40ec87a7cf/rre.schema.json
+apiVersion: backstage.io/v1alpha1
+kind: Resource
+metadata:
+  name: buildkite-pipeline-elasticsearch-pull-request-performance-benchmark
+  description: Elasticsearch pull request performance benchmark
+  links:
+    - title: Pipeline
+      url: https://buildkite.com/elastic/elasticsearch-pull-request-performance-benchmark
+spec:
+  type: buildkite-pipeline
+  system: buildkite
+  owner: group:elasticsearch-team
+  implementation:
+    apiVersion: buildkite.elastic.dev/v1
+    kind: Pipeline
+    metadata:
+      description: ":elasticsearch: Runs performance benchmark in the PR context"
+      name: elasticsearch / pull-request / performance-benchmark
+    spec:
+      repository: elastic/elasticsearch
+      pipeline_file: .buildkite/pipelines/pull-request/performance-benchmark.yml
+      env:
+        ELASTIC_PR_COMMENTS_ENABLED: "true"
+        ELASTIC_SLACK_NOTIFICATIONS_ENABLED: "true"
+        SLACK_NOTIFICATIONS_CHANNEL: "#es-perf-build"
+        SLACK_NOTIFICATIONS_ALL_BRANCHES: "false" # TODO: change to true later
+      teams:
+        elasticsearch-team: {}
+        ml-core: {}
+        everyone:
+          access_level: BUILD_AND_READ
+      provider_settings:
+        build_pull_requests: true
+        trigger_mode: none