[tamnd]

The 7.2.8 and 6.12.111 A64 nightlies with the distro configs ran out of time in rk test, so neither wrote a test.json. The 7.2.8 record showed where the time went.

• The kunit boot timed out on both kernels at 2400 seconds. The reference had loaded 4216 of its 5834 modules by then. A kunit boot now gets one more second for each module it loads, in rk test and in rk cross-modules alike.
• landlock's fs_bench took 26 minutes of the reference's boot and the whole rest of the rucc kernel's. It is a benchmark that walks a path 10000 directories deep 100000 times, so it is left out of the list the boots run.
• rk cross-modules refused nearly every module in both crossed boots with "failed to validate module BTF: -22". A module's BTF is split BTF on top of its own vmlinux's, so it never validates in the other build's kernel. The test fragments for E10 and E11 now turn on MODULE_ALLOW_BTF_MISMATCH, so the kernel drops the module's BTF with a warning and still checks the CRCs.
• On A64 the boots run four at a time instead of two. Most suites keep one of a guest's two CPUs busy, and TCG lets an idle one sleep.
• A manual run can name the kinds rk test grades, so a distro night can be split into a kunit run and a selftests and LTP run. rk cross-modules only runs when kunit is one of them.

Part of #7.