[Feature Request]: Support Resource Dir through CppInterOp

[anutosh491]

Description of new feature

Two main reasons why this would be helpful is that

1. Xeus-cpp's non-wasm based kernels can make use of it through kernel.json

  "argv": [
      "/Users/anutosh491/micromamba/envs/xeus-cpp/bin/xcpp",
      "-f",
      "{connection_file}",
      "-resource-dir", "/Users/anutosh491/micromamba/envs/xeus-cpp/lib/clang/19",
      "-I", "/Users/anutosh491/micromamba/envs/xeus-cpp/include",
      "-std=c++20"
  ]

Currently we do provide a location "/Users/anutosh491/micromamba/envs/xeus-cpp/lib/clang/19" but this is just a placeholder right now and such a location doesn't exist during the setup.

2. Xeus-cpp's wasm based kernel can make use of it through emscripten's preloading feature (--preload-file or --embed-file

Once we have a resource dir through cppinterop, we just move these files to dedicated location that also has contains emscripten's sysroot and then we preload all of these files together.

[anutosh491]

IIRC some discussion was done on discord for the same but not sure we had a concrete way forward. Opening an issue to keep track of the same.
Maybe someone could educate me with what needs to be done if we have a solution.

[mcbarton]

@anutosh491 @vgvassilev If we build the resource directory as part of the build process then we can mount it the virtual file system of the Jupyter lite build. When mounting we can pick the exact location of the resource dir. Its one of the options of the Jupyter lite build, so would be simple to implement.