ci: Remove .build-rules from core test job definitions.

If you accidentally re-included your test job core definition after your
driver-specific ruleset, you'd end up running the driver job on every
source code change.  This had happened with a630_gles_asan: it included
.baremetal-test-arm64-asan (and thus .baremetal-test) after including
.a630-test, to override .baremetal-test-arm64's depednencies to use asan
artifacts instead.

Acked-by: Michel Dänzer <mdaenzer@redhat.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17386>

.gitlab-ci/lava/lava-gitlab-ci.yml

@@ -1,6 +1,4 @@
 .lava-test:
-  extends:
-    - .build-rules
   # Cancel job if a newer commit is pushed to the same branch
   interruptible: true
   variables:

.gitlab-ci/test/gitlab-ci.yml

@@ -1,6 +1,4 @@
 .test:
-  extends:
-    - .build-rules
   # Cancel job if a newer commit is pushed to the same branch
   interruptible: true
   variables:
@@ -116,7 +114,6 @@
 
 .baremetal-test:
   extends:
-    - .build-rules
     - .test
   # Cancel job if a newer commit is pushed to the same branch
   interruptible: true