Add Addressables as a direct dependency and settings, Content group entry

Cut 1 of docs/addressables-cut.md: com.unity.addressables becomes a
direct manifest dependency (was transitive via com.unity.localization),
Addressables settings are created with BuildWithPlayer forced instead of
left as a per-user preference, and Assets/Content is added to the
Default Local Group as the one folder entry Cut 2 will populate (Q1
ruling A). No code loads through Addressables yet and the folder is
empty, so this lands harmlessly on its own.

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

Packages/manifest.json

@@ -2,6 +2,7 @@
   "dependencies": {
     "com.unity.2d.sprite": "1.0.0",
     "com.unity.2d.tilemap": "1.0.0",
+    "com.unity.addressables": "2.9.1",
     "com.unity.ai.navigation": "2.0.14",
     "com.unity.burst": "1.8.30",
     "com.unity.cinemachine": "2.10.7",

Packages/packages-lock.json

@@ -17,7 +17,7 @@
     },
     "com.unity.addressables": {
       "version": "2.9.1",
-      "depth": 1,
+      "depth": 0,
       "source": "registry",
       "dependencies": {
         "com.unity.profiling.core": "1.0.2",
@@ -165,7 +165,7 @@
     },
     "com.unity.profiling.core": {
       "version": "1.0.3",
-      "depth": 2,
+      "depth": 1,
       "source": "registry",
       "dependencies": {},
       "url": "https://packages.unity.com"
@@ -183,7 +183,7 @@
     },
     "com.unity.scriptablebuildpipeline": {
       "version": "2.6.1",
-      "depth": 2,
+      "depth": 1,
       "source": "registry",
       "dependencies": {
         "com.unity.test-framework": "1.4.5",