`new Intl.Segmenter().segment()` causes SEGFAULT with `--with-intl=small-icu` and no runtime ICU data

### Version v20.10.0 ### Platform Linux acfbcf435a24 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024 x86_64 GNU/Linux ### Subsystem Intl ### What steps will reproduce the bug? 1. Obtain a nodejs build compiled with `--with-intl=small-icu`.* 2. Execute `new Intl.Segmenter().segment()` in the REPL. *In my case that was the nodejs package from Fedora 39 *without* nodejs-full-i18n. This can be obtained as follows: 1. Create a docker/podman container with Fedora 39: `podman run --rm -it fedora:39` 2. `dnf install -y --setopt=install_weak_deps=False nodejs` ### How often does it reproduce? Is there a required condition? Always, as long as *no* [runtime ICU data](https://nodejs.org/docs/latest-v20.x/api/intl.html#providing-icu-data-at-runtime) is present. ### What is the expected behavior? Why is that the expected behavior? NodeJS should fallback to a locale-unaware string separator, not provide `Intl.Segmenter` at all, or raise a JS exception. The status quo offers no possibility to know if segmentation is safe and calling it results in a segmentation fault and therefore instant termination of the process. ### What do you see instead? A segmentation fault ### Additional information <details> <summary>Backtrace</summary> ``` Core was generated by `node'. Program terminated with signal SIGSEGV, Segmentation fault. #0 v8::internal::JSSegments::Create () at ../../deps/v8/src/objects/js-segments.cc:33 33 segmenter->icu_break_iterator().raw()->clone(); [Current thread is 1 (Thread 0x7f0039bc7c40 (LWP 49))] (gdb) bt #0 v8::internal::JSSegments::Create () at ../../deps/v8/src/objects/js-segments.cc:33 #1 0x00007f003c910b24 in Builtin_Impl_SegmenterPrototypeSegment () at ../../deps/v8/src/builtins/builtins-intl.cc:1170 #2 v8::internal::Builtin_SegmenterPrototypeSegment () at ../../deps/v8/src/builtins/builtins-intl.cc:…