tests: benchmarks: optimize filters and use platform_key.

Benchmarks are not tests, we run them to verify they still work and do
not bitrot. Running them on each architecture should be sufficient.

This reduces amount of churn in CI and still allows them to be run
individually on platforms.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>

tests/benchmarks/app_kernel/testcase.yaml

@@ -1,4 +1,6 @@
 common:
+  platform_key:
+    - arch
   tags:
     - benchmark
     - kernel

tests/benchmarks/data_structure_perf/dlist_perf/testcase.yaml

@@ -1,5 +1,7 @@
 tests:
   benchmark.data_structure_perf.dlist:
+    platform_key:
+      - arch
     tags:
       - benchmark
       - dlist

tests/benchmarks/data_structure_perf/rbtree_perf/testcase.yaml

@@ -1,5 +1,7 @@
 tests:
   benchmark.data_structure_perf.rbtree:
+    platform_key:
+      - arch
     tags:
       - benchmark
       - rbtree

tests/benchmarks/latency_measure/testcase.yaml

@@ -1,4 +1,6 @@
 common:
+  platform_key:
+    - arch
   tags:
     - kernel
     - benchmark

tests/benchmarks/sched/testcase.yaml

@@ -1,5 +1,7 @@
 tests:
   benchmark.kernel.scheduler:
+    platform_key:
+      - arch
     tags:
       - benchmark
       - kernel

tests/benchmarks/sched_queues/testcase.yaml

@@ -1,4 +1,7 @@
 common:
+  platform_key:
+    - arch
+  min_ram: 32
   tags:
     - kernel
     - benchmark

tests/benchmarks/sched_userspace/testcase.yaml

@@ -5,7 +5,6 @@ tests:
       - kernel
       - benchmark
       - userspace
-    slow: true
     filter: CONFIG_ARCH_HAS_USERSPACE
     arch_exclude:
       - posix

tests/benchmarks/sys_kernel/testcase.yaml

@@ -1,5 +1,7 @@
 tests:
   benchmark.kernel.core:
+    platform_key:
+      - arch
     tags:
       - kernel
       - benchmark

tests/benchmarks/thread_metric/testcase.yaml

@@ -1,4 +1,6 @@
 common:
+  platform_key:
+    - arch
   tags:
     - kernel
     - benchmark

tests/benchmarks/wait_queues/testcase.yaml

@@ -1,4 +1,6 @@
 common:
+  platform_key:
+    - arch
   tags:
     - kernel
     - benchmark