We need to revisit our emscripten / emsdk approach. The emsdk rules on envoy were changed from 1.20 to 1.22 therefore our current rules applied on OSSM 2.2 do not work.

Our current (2.2) approach is to rely on /opt/emsdk containing all necessary files. This is no longer valid in 2.3 as the bazel rules changed. An initial attempt to run the vendor script resulted in creation of directories for emscripten and node, with 2.0GB in size. We need to workaround that the same way we did for 2.1 and 2.2.

Envoy 1.22 uses emsdk / emscripten 3.1.7. Current Red Hat's emsdk version is 2.0.15. We need to update it.