Scaffold NCS firmware project structure

Sets up kvida-os as a freestanding nRF Connect SDK application for the
nRF54L15, pinned to NCS v3.4.0, with a Docker/WSL2 build environment
(toolchain-only image, NCS modules fetched into a separate volume at
first run) and placeholder module directories matching the architecture
described in the kvida meta-repo.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

docker-compose.yml

@@ -0,0 +1,25 @@
+services:
+  build:
+    build:
+      context: .
+      dockerfile: docker/Dockerfile
+    working_dir: /workspace
+    volumes:
+      # West workspace topdir: holds .west/, and the NCS/Zephyr module
+      # tree fetched by `west update` (nrf/, zephyr/, modules/, ...).
+      - ncs-workspace:/workspace
+      # This repo, bind-mounted as the manifest project inside the
+      # workspace (matches `self.path: kvida-os` in west.yml).
+      - .:/workspace/kvida-os
+    tty: true
+    # USB/J-Link access (for `west flash`) is expected to be handled via
+    # usbipd-win forwarding the probe into WSL2. If `west flash` needs to
+    # run inside this container rather than on the WSL2 host, uncomment
+    # and adjust one of the following once the forwarded device node is
+    # known:
+    # devices:
+    #   - "/dev/bus/usb:/dev/bus/usb"
+    # privileged: true
+
+volumes:
+  ncs-workspace: