E2E runs Milo v0.32.5 while production runs v0.36.5 #670

Summary

The e2e environment ran Milo v0.32.5, and production runs v0.36.5. Before v0.36.3, Milo names its identity models in a form the OpenAPI v2 parser in kubectl cannot resolve (milo-os/milo#838).

Bring-ups that applied a fixture while Milo served only v2 failed on a schema error: 44 of 328 e2e attempts from 2026-10-01 to 2026-10-14. I moved e2e to v0.36.5 in #669.

Acceptance criteria

• e2e runs the Milo release production runs (chore: Run e2e on Milo v0.36.5, whose OpenAPI v2 kubectl can parse #669)