overrides: pin to kernel-5.15.7-200.fc35

Newer kernels seem to have an issue with enhanced networking on some
AWS instance types so they don't boot. Let's pin on the older kernel
for now while we investigate and find a proper solution.

See coreos/fedora-coreos-tracker#1066

(cherry picked from commit 467af82)

manifest-lock.aarch64.json

@@ -463,13 +463,13 @@
       "evra": "2.4.0-8.fc35.noarch"
     },
     "kernel": {
-      "evra": "5.15.12-200.fc35.aarch64"
+      "evra": "5.15.7-200.fc35.aarch64"
     },
     "kernel-core": {
-      "evra": "5.15.12-200.fc35.aarch64"
+      "evra": "5.15.7-200.fc35.aarch64"
     },
     "kernel-modules": {
-      "evra": "5.15.12-200.fc35.aarch64"
+      "evra": "5.15.7-200.fc35.aarch64"
     },
     "kexec-tools": {
       "evra": "2.0.22-7.fc35.aarch64"

manifest-lock.overrides.yaml

@@ -8,4 +8,19 @@
 # in the `metadata.reason` key, though it's acceptable to omit a `reason`
 # for FCOS-specific packages (ignition, afterburn, etc.).
 
-packages: {}
+packages:
+  kernel:
+    evr: 5.15.7-200.fc35
+    metadata:
+      reason: https://github.com/coreos/fedora-coreos-tracker/issues/1066
+      type: pin
+  kernel-core:
+    evr: 5.15.7-200.fc35
+    metadata:
+      reason: https://github.com/coreos/fedora-coreos-tracker/issues/1066
+      type: pin
+  kernel-modules:
+    evr: 5.15.7-200.fc35
+    metadata:
+      reason: https://github.com/coreos/fedora-coreos-tracker/issues/1066
+      type: pin

manifest-lock.x86_64.json

@@ -469,13 +469,13 @@
       "evra": "2.4.0-8.fc35.noarch"
     },
     "kernel": {
-      "evra": "5.15.12-200.fc35.x86_64"
+      "evra": "5.15.7-200.fc35.x86_64"
     },
     "kernel-core": {
-      "evra": "5.15.12-200.fc35.x86_64"
+      "evra": "5.15.7-200.fc35.x86_64"
     },
     "kernel-modules": {
-      "evra": "5.15.12-200.fc35.x86_64"
+      "evra": "5.15.7-200.fc35.x86_64"
     },
     "kexec-tools": {
       "evra": "2.0.22-7.fc35.x86_64"