fix: target_compatible_with excluding arm64 (#84)

* fix: target_compatible_with excluding arm64

The 'ci: update ci and exclude windows' commit added
'target_compatible_with' arguments to some of the tests restricting them
to linux but it also forced amd64 instead of allowing the tests to run
in both linux/amd64 and linux/arm64.

Before this fix, I would get SKIPPED tests when testing on linux/arm64
and now all the tests run.

* chore: updating locks

Just doing 'bazel run' on the locks (except apt_security which is
lock-less) and runnign the tests for linux/amd64 and linux/arm64:

```
bazel run @bullseye//:lock
bazel run @shared_dependencies//:lock
bazel run @noble//:lock

bazel test //...
```

produces these changes, which seem to be, mostly,

* tabs vs 2 spaces in lock.json
* keys with '_' instead of '~'
* some tooling in MODULES.lock

e2e/smoke/BUILD

@@ -120,8 +120,10 @@ container_structure_test(
         "@platforms//cpu:x86_64": ["test_linux_amd64.yaml"],
     }),
     image = ":apt",
-    target_compatible_with = [
-        "@platforms//cpu:x86_64",
+    target_compatible_with = select({
+        "@platforms//cpu:x86_64": ["@platforms//cpu:x86_64"],
+        "@platforms//cpu:arm64": ["@platforms//cpu:arm64"],
+    }) + [
         "@platforms//os:linux",
     ],
 )

examples/debian_shared_dependencies/BUILD.bazel

@@ -107,8 +107,10 @@ container_structure_test(
         "@platforms//cpu:x86_64": ["test_linux_amd64.yaml"],
     }),
     image = ":apt",
-    target_compatible_with = [
-        "@platforms//cpu:x86_64",
+    target_compatible_with = select({
+        "@platforms//cpu:x86_64": ["@platforms//cpu:x86_64"],
+        "@platforms//cpu:arm64": ["@platforms//cpu:arm64"],
+    }) + [
         "@platforms//os:linux",
     ],
 )