fix: install nRF Cloud libraries from NPM instead of JSR

These libraries are published to NPM now, so consume them as ordinary registry
dependencies instead of through JSR's NPM compatibility layer
(`npm:@jsr/nrfcloud__…`).

This also removes `@jsr:registry` and `allow-remote` from `.npmrc`. Nothing is
installed from JSR anymore, and `allow-remote` only existed to permit JSR's
remote tarball URLs, which NPM v12 blocks by default. Keeping it would leave
remote tarball fetches enabled for every dependency in the tree for no reason.

Author: coderbyheart

.npmrc

@@ -34,7 +34,7 @@
   },
   "devDependencies": {
     "@bifravst/prettier-config": "1.1.17",
-    "@nrfcloud/validate-with-typebox": "npm:@jsr/nrfcloud__validate-with-typebox@^1.0.5",
+    "@nrfcloud/validate-with-typebox": "^1.0.6",
     "@swc/core": "1.15.47",
     "@types/aws-lambda": "8.10.162",
     "@types/node": "25.9.5",
@@ -69,7 +69,7 @@
     "@aws-lambda-powertools/metrics": "2.34.0",
     "@middy/core": "7.7.2",
     "@middy/input-output-logger": "7.7.2",
-    "@nrfcloud/problem-detail": "npm:@jsr/nrfcloud__problem-detail@1.4.2",
+    "@nrfcloud/problem-detail": "1.4.3",
     "@sinclair/typebox": "0.34.52"
   }
 }