fix(codegen): path-specific drops for struct return from nested scopes

[slepp]

Fixes struct return from nested scopes (if/for/while) returning the wrong value and leaking the non-returned variable.

Problem

return StructType{...} from inside nested control flow returned the trailing expression value instead of the early return value, because initReturnFlagAndSlot excluded aggregate types from returnSlot creation. Additionally, non-returned variables were never dropped — a memory leak.

Solution

Lazy returnSlot creation with path-specific drop semantics:

• ensureReturnSlot(): creates return slot lazily for aggregate types at the function entry block
• earlyReturnFlag: distinguishes explicit return statements from trailing expressions for drop path selection
• Pre-scan with hasNestedReturn: detects nested returns before body generation to enable return guards
• Path-specific drops: scf.if(earlyReturnFlag) with separate exclusion sets per branch
• Struct alloca promotion: extends declareVariable promotion to struct types (gated by returnSlotIsLazy) with zeroinitializer
• Struct null-guard: checks first pointer/integer field before calling user-defined Drop on potentially uninitialized structs

Tests

3 new E2E tests covering struct return from if-body, for-loop, and outer-scope variable return. All 530 E2E tests pass.

[slepp]

Superseded by #284 which applies this fix rebased onto current main (after 6 major merges to the drop/RAII system). The bug was confirmed to still reproduce on main — the RAII leak audit (#277) did not address the aggregate-type returnSlot gap.