feat(rung10): the python dies - body, tests, and their CI jobs

[godon-robot]

The motion (queue item 2, after #125's merge)

Per the holder's re-plan: only he runs the estate, the repo's python has no external readers (windmill runs its own synced script copies), and the ported rust suite is the parity record. The python goes in one motion.

What dies

• controller/ - 30 files: the verb scripts, both services, both grammars, the database layer, config, and the two executors (the create-executor was the last body to gain its rust twin in feat(rung10): the create-executor ports - the last python body #125)
• shared/otel_logging.py
• tests/conftest.py + tests/unit/ - 12 python test files. Every one of them is ported: systemtenders (test(rung10): the systemtenders suite ported #121/fix(rung10): the three the main build caught #122/feat(rung10): the create-executor ports - the last python body #125), steerwishes (test(rung10): the wishes suite — the last python test file ported #123), instruments read (test(rung10): the port harness round two + the instruments read port #120), and the four harness-level files (test(rung10): the python test-suite port - the parity bar #118/test(rung10): the port harness round two + the instruments read port #120)
• the two python CI workflows (Controller CI's postgres integration job, Controller Unit Tests' pytest job). cargo test is the check from here on - the standing parity record

What deliberately stays (named, for the wiring motions)

• both component.yamls - the windmill sync specs. With the python gone their patterns match nothing; they get rebuilt as header scripts + pointer files in queue item 5, not silently edited here
• the README (describes the domain, not the file layout)
• the windmill path strings f/controller/* inside the rust tree - surface contract, motion 5's seam
• provenance notes ("ported from controller/systemtender_service.py") - they document where the port came from

Riders, same seam

• the now-false SKIPPED marker in tests/port/wishes.rs ("the create-executor tests, python leaf by ruling" - they landed in systemtenders.rs with feat(rung10): the create-executor ports - the last python body #125)
• three present-tense notes claiming the python suite under tests/unit/ is the parity bar / stays the reference until cutover (database.rs tail, tests/port/main.rs, tests/rust/main.rs) - reworded to the new truth: this suite is the standing record

The estate is untouched: nothing coexists at the reinstall - it picks up the finished artifact (factory image, probe, header scripts still queued).

After this merge, next in order: the factory image in godon-images, the yugabyte probe as an actions job, then header scripts + pointer files.

Co-authored-by: cherusk 10729954+cherusk@users.noreply.github.com