Fix memory/table segment checks in memory.init/table.init

[wenyongh]

According to the wasm core spec, the checks for the table segments in
table.init opcode are similar to the checks for memory.init opcode:

• The size of a passive segment is shrunk to zero after data.drop
  (or elem.drop) opcode is executed, but it can be used to do
  memory.init (or table.init) again
• The memory.init only traps when s+n > len(data.data) or d+n > len(mem.data)
  and table.init only traps when s+n > len(elem.elem) or d+n > len(tab.elem)
• The active segment can also be used to do memory.init (or
  table.init), while it behaves like a dropped passive segement

https://github.com/WebAssembly/bulk-memory-operations/blob/master/proposals/bulk-memory-operations/Overview.md

Segments can also be shrunk to size zero by using the following new instructions:
- data.drop: discard the data in an data segment
- elem.drop: discard the data in an element segment

An active segment is equivalent to a passive segment, but with an implicit
memory.init followed by a data.drop (or table.init followed by a elem.drop)
that is prepended to the module's start function.

ps.
https://webassembly.github.io/spec/core/bikeshed/#-hrefsyntax-instr-memorymathsfmemoryinitx%E2%91%A0
https://webassembly.github.io/spec/core/bikeshed/#-hrefsyntax-instr-tablemathsftableinitxy%E2%91%A0
#3020