Add dynamic resident program lifecycle

[espmaniac]

Summary

• add m3_DylinkAddProgram, m3_DylinkRemoveProgram, and m3_DylinkGetProgramCount
• keep resident shared libraries alive while applications are added and removed independently
• give each application stable context storage plus private linear-memory, stack, heap, and table ranges
• recycle released linear-memory and table ranges without shrinking the shared runtime allocation
• park an empty dynamic group so it can accept another application later
• document the dynamic lifecycle API and its memory behavior

Validation

• strict native compilation with dylink enabled and disabled
• strict native compilation with M3C enabled
• full native runner linked against all wasm3 sources
• real dylink.0 lifecycle: add, run, remove, reopen, and preserve resident-library state
• AddressSanitizer and UndefinedBehaviorSanitizer run (leak detection disabled because it is incompatible with the traced runner)

Integration coverage is added in the dependent wasm-rtos-tests PR.