Memory: improve error handling for "out of bounds memory access"

[evacchi]

• Current exception message does not carry any information about where the error occurred
• Moreover, the exception is often raised by catching an IndexOutOfBoundsException, even when we are already aware of the limits; we should be able to check those limits explicitly, avoiding an expensive exception to be created

[electrum]

While I generally agree about not creating exceptions needlessly, does it actually matter here? When OOB access occurs, the WASM program is terminated.

I just noticed that Memory has a mix of UninstantiableException and WasmRuntimeException, which should be cleaned up.