Fix Redline native memory growth, atomics, wait/notify and traps

[andreaTP]

Follow-up to the review of #230. Both native memories, Panama and JFFI, get the same fixes:

• an initial size over RUNTIME_MAX_PAGES is rejected instead of being mapped past the reservation, into a neighbouring mapping
• grow() is synchronized and the memory view is volatile, so concurrent grows can't hand out the same page and host readers see the current size
• running guest code sees growth by another instance sharing the memory, through a page count the memory owns, and growth by a host import
• host atomics are hardware atomics, so they no longer lose updates against the guest's
• wait/notify get the Runtime: fix lost wakeup from late-arriving atomicWaitBroken wait notify #107 lost-wakeup fix and throw WasmInterruptedException when interrupted
• a trap recorded by the runner's Java handler (memory.init, data.drop, table operations, memory.grow, wait/notify) stops the guest at once
• a length-0 memory.init on a dropped segment still checks its offsets

The .native format moves to version 3, since compiled code reads a new context slot.

cc. @andreas-karlsson