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>

west.yml

@@ -0,0 +1,23 @@
+# West manifest for kvida-os (freestanding NCS application).
+#
+# This repo is meant to sit as a named subdirectory ("kvida-os") inside a
+# west workspace topdir, e.g. `/workspace/kvida-os`. Running
+# `west init -l kvida-os && west update` from the topdir fetches sdk-nrf
+# (which pulls in Zephyr, MCUboot, Matter, etc. via its own manifest) as
+# siblings of this repo (`/workspace/nrf`, `/workspace/zephyr`, ...).
+#
+# Pinned to NCS v3.4.0.
+manifest:
+  remotes:
+    - name: ncs
+      url-base: https://github.com/nrfconnect
+
+  projects:
+    - name: nrf
+      remote: ncs
+      repo-path: sdk-nrf
+      revision: v3.4.0
+      import: true
+
+  self:
+    path: kvida-os