Add workaround in dev docs for issue with OpenSearch image

[facutuesca]

Building the OpenSearch image in a M4 Macbook results in the following error:

 => CACHED [opensearch 1/6] FROM docker.io/opensearchproject/opensearch:2.12.0@sha256:645d3d9390ade7ebef988d3c9bc61a6616f1863ff41efe97e2347d6bf7972504                                 0.0s
 => ERROR [opensearch 2/6] RUN opensearch-plugin remove opensearch-skills --purge                                                                                                      0.2s
------
 > [opensearch 2/6] RUN opensearch-plugin remove opensearch-skills --purge:
0.160 #
0.160 # A fatal error has been detected by the Java Runtime Environment:
0.160 #
0.160 #  SIGILL (0x4) at pc=0x0000f819dfc67c5c, pid=25, tid=26
0.160 #
0.160 # JRE version:  (21.0.2+13) (build )
0.160 # Java VM: OpenJDK 64-Bit Server VM (21.0.2+13-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
0.160 # Problematic frame:
0.160 # j  java.lang.System.registerNatives()V+0 [email protected]
0.160 #
0.160 # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /usr/share/opensearch/core.25)
0.160 #
0.160 # An error report file with more information is saved as:
0.160 # /usr/share/opensearch/hs_err_pid25.log
0.163 [0.010s][warning][os] Loading hsdis library failed
0.166 #
0.166 # The crash happened outside the Java Virtual Machine in native code.
0.166 # See problematic frame for where to report the bug.
0.166 #
0.211 /usr/share/opensearch/bin/opensearch-env: line 99:    25 Aborted                 (core dumped) "$JAVA" "$XSHARE" -cp "$OPENSEARCH_CLASSPATH" org.opensearch.tools.java_version_checker.JavaVersionChecker

This seems to be a known issue with M4 processors. A workaround is described here: comment

This PR documents that workaround in the troubleshooting section of the warehouse dev docs.

cc @woodruffw

[woodruffw]

Thanks @facutuesca, LGTM!

[miketheman]

Curious - this link is from the elasticsearch-side on the world, and we're using opensearch. Is it possible that's been fixed over there / possibly in another version, or something else?

[woodruffw]

@facutuesca can confirm, but I believe the issue is present in both -- based on the discussion in that issue, users are seeing the both the same crash and have the same fix.