Reland "[wasm] Fix two jump table offset parameters."

This is a reland of 74951850

Original change's description:
> [wasm] Fix two jump table offset parameters.
> 
> R=jgruber@chromium.org
> 
> Change-Id: I5b40819b1a746f16b7b18aac1bba65d83a7e3483
> Reviewed-on: https://chromium-review.googlesource.com/c/1470127
> Reviewed-by: Jakob Gruber <jgruber@chromium.org>
> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#59560}

Change-Id: I70b814f81bfd0c13e09a2641871da2d4ec5a308d
Reviewed-on: https://chromium-review.googlesource.com/c/1470111Reviewed-by: Maya Lekova <mslekova@chromium.org>
Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#59597}

src/wasm/wasm-code-manager.cc

@@ -747,8 +747,8 @@ WasmCode* NativeModule::CreateEmptyJumpTable(uint32_t jump_table_size) {
                       instructions.as_vector(),       // instructions
                       0,                              // stack_slots
                       0,                              // tagged_parameter_slots
-                      instructions.size(),            // safepoint_table_offset
-                      instructions.size(),            // handler_table_offset
+                      0,                              // safepoint_table_offset
+                      0,                              // handler_table_offset
                       instructions.size(),            // constant_pool_offset
                       instructions.size(),            // code_comments_offset
                       instructions.size(),            // unpadded_binary_size