fix(runtime): tolerate sandbox-denied parents in exact-case path checks (#66)

PathExistsWithExactCase verifies each component by enumerating its parent
directory, starting from the filesystem root. On a physical device the
sandbox forbids listing everything above the app container
(/private/var/containers, /var/mobile/Containers), so the directory iterator
errors and every module resolution failed with "the specified module does
not exist" - the runtime could not boot any app on hardware while the
simulator (whose containers live under the listable macOS home) passed. When
a parent cannot be enumerated, trust the exists() check that already vouched
for the full path and keep walking: case verification still applies to every
listable level, which covers the app's own content - the case mistakes the
check exists to catch.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: NathanWalker

NativeScript/runtime/modules/module/ModuleInternal.cpp

@@ -15,8 +15,8 @@
 #include <unordered_map>
 #include <unordered_set>
 
-#include "runtime/NativeScriptException.h"
 #include "native_api_util.h"
+#include "runtime/NativeScriptException.h"
 #include "runtime/RuntimeConfig.h"
 #include "runtime/Util.h"
 #include "runtime/modules/node/Node.h"
@@ -173,7 +173,14 @@ bool PathExistsWithExactCase(const std::filesystem::path& path) {
       }
     }
 
-    if (iterEc || !matched) {
+    if (iterEc) {
+      // On device the sandbox forbids enumerating everything above the app
+      // container (/private/var/...), so case verification is only possible
+      // for listable levels; exists() already vouched for the full path.
+      current /= component;
+      continue;
+    }
+    if (!matched) {
       return false;
     }