We need to register the unwind info for each code space (it was just
done for the first one). Otherwise we fail when freeing the native
module, where we try to unregister the unwind info again for each code
space.

This CL moves the call to {RegisterNonABICompliantCodeRange} from
{NewNativeModule} to {AddCodeSpace}, so it happens whenever a new code
space is added.

R=jgruber@chromium.org
CC=​paolosev@microsoft.com

Bug: chromium:1008597, v8:9477, v8:9795
Change-Id: I20121b2a2fde4d37432dd7e13b19cdf99129e6a4
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832178
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64078}