HaveOffsetConverter import missing in WASM module built with proxy-wasm-cpp-sdk

[ramachaitanyak]

When building a WASM module using the proxy-wasm-cpp-sdk and running it in Envoy, the module fails to load due to a missing import:

[2025-12-21 00:32:01.513][286][debug][wasm] Base Wasm created 1 now active
[2025-12-21 00:32:01.922][286][error][wasm] Failed to load Wasm module due to a missing import: env.HaveOffsetConverter
[2025-12-21 00:32:01.922][286][error][wasm] Wasm VM failed Failed to initialize Wasm code
[2025-12-21 00:32:01.922][286][debug][wasm] ~Wasm 0 remaining active

Steps to reproduce:

1. Build a WASM module using the proxy-wasm-cpp-sdk with the current default build flags.
2. Start Envoy with the WASM filter pointing to the built module.
3. Observe the error in the logs above.

Expected behavior:

The module should load and run correctly in Envoy without requiring HaveOffsetConverter.

Notes:

1. Using PROXY_WASM_DISABLE_OFFSET_CONVERTER or similar flags does not seem to prevent the HaveOffsetConverter symbol from being included in the compiled module.
2. The issue appears related to ABI compatibility between the proxy-wasm-cpp-sdk and Envoy’s WASM runtime.
3. WASM module BUILD :
envoy_wasm_cc_binary(
    name = "shield_ingestor.wasm",
    srcs = [
        ....
    ],
    deps = [
        "@proxy_wasm_cpp_sdk//:proxy_wasm_intrinsics_lite",
         ....
    ],