V3 remaining failure groups

These files split the remaining V3 failures into non-overlapping groups for
parallel fix sessions.

Groups:
- 01_stdlib_services.txt: crypto, db, net, veb, and x modules (0)
- 02_stdlib_other_and_tools.txt: cmd, examples, and other non-vlib/v modules (0)
- 03_v_compiler_infra.txt: vlib/v tests outside vlib/v/tests (0)
- 04_v_tests_generics.txt: vlib/v/tests generics and generic root tests (0)
- 05_v_tests_comptime_and_options.txt: comptime and option tests (0)
- 06_v_tests_fns_and_control_flow.txt: fns, conditions, loops, concurrency (0)
- 07_v_tests_collections_aliases_casts.txt: arrays, maps, strings, aliases, casts (0)
- 08_v_tests_types_interfaces_sumtypes.txt: interfaces, structs, pointers, unions,
  and sum types (0)
- 09_v_tests_misc_language_projects.txt: remaining vlib/v/tests language/project
  tests (0)

Resolved ORM tests are tracked in test_passes.txt. The host-blocked MySQL ORM
test remains in test_skipped.txt because its native SDK is unavailable. Do not
add ORM tests back to these groups without a strict no-fallback failure.

The vlib/x/atomics tests (i32/i64/u32/u64) are tracked in test_skipped.txt:
that module implements its API only via amd64/i386 inline assembly and has no
arm64 backend, so the tests do not compile on arm64 hosts with any V compiler
(V 0.5.2 fails identically). They are a platform gap in the module, not a v3
compiler failure.

When a session fixes a group, re-check that group and update both the master
pass/failure lists and the relevant group file.
