Run remote-kubernetes-net-test on config changes as well (#4826)

## Motivation

Right now if we change the configs and break things for the kubernetes
deployment, it won't be caught by CI

## Proposal

Make sure that for the `remote-kubernetes-net-test` we also run it on
config changes, or `Dockerfile` changes.

## Test Plan

CI

## Release Plan

- Nothing to do / These changes follow the usual release cycle.

Author: ndr-ds

.github/workflows/rust.yml

@@ -50,11 +50,26 @@ jobs:
           filters: |
             paths:
               - '!docker/**'
-              - '!docker_scylla/**'
               - '!configuration/**'
               - '!kubernetes/**'
               - '!CONTRIBUTING.md'
               - '!INSTALL.md'
+  changed-files-kubernetes:
+    runs-on: ubuntu-latest
+    outputs:
+      should-run: ${{ steps.files-changed.outputs.paths }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Filter paths
+        uses: dorny/paths-filter@v3
+        id: files-changed
+        with:
+          predicate-quantifier: 'every'
+          filters: |
+            paths:
+              - '!configuration/**'
+              - '!CONTRIBUTING.md'
+              - '!INSTALL.md'
   remote-net-test:
     needs: changed-files
     if: needs.changed-files.outputs.should-run == 'true'
@@ -94,8 +109,8 @@ jobs:
         cargo test -p linera-service remote_net_grpc --features remote-net
 
   remote-kubernetes-net-test:
-    needs: changed-files
-    if: needs.changed-files.outputs.should-run == 'true'
+    needs: changed-files-kubernetes
+    if: needs.changed-files-kubernetes.outputs.should-run == 'true'
     runs-on: ubuntu-latest-16-cores
     timeout-minutes: 90