fix(parser): correct multi-memory memarg field ordering

[avrabe]

Summary

• Fix memarg binary encoding order: the multi-memory proposal encodes fields as align, memidx?, offset — we were reading align, offset, memidx?
• This caused all multi-memory modules to fail with misaligned bytecode parsing
• Fixes ~275 WAST test assertions (address0.wast, address1.wast now fully pass)

Test plan

• address0.wast: 0/92 → 92/92 passing
• address1.wast: 0/127 → 127/127 passing
• Full WAST suite: 62,351 → 62,626 passing (95.4%)

Trace: skip

🤖 Generated with Claude Code

[github-actions]

🔍 Build Diagnostics Report

Summary

Metric	Base Branch	This PR	Change
Errors	0	0	0
Warnings	2	2	0

🎯 Impact Analysis

Issues in Files You Modified

• 0 new errors introduced by your changes
• 0 new warnings introduced by your changes
• 0 total errors in modified files
• 0 total warnings in modified files
• 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

• 0 new errors in unchanged files
• 0 new warnings in unchanged files
• 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.

---

📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning