rename: Jarvis -> Jervis target, scheme, and folder throughout

The bundle-ID and display-name renames weren't enough — the actual
Xcode target/product name was still "Jarvis", which drives CFBundleName,
Xcode's Organizer archive list, the .xcodeproj filename, and the scheme
name. Renamed all the way through:

- project.yml: top-level name, target key, PRODUCT_NAME, source/info paths
- Jarvis/ -> Jervis/ (source folder, git-tracked as renames, no content
  diffs on the moved files)
- .gitignore, CI workflows, README, CONTRIBUTING: Jarvis.xcodeproj /
  scheme Jarvis -> Jervis.xcodeproj / scheme Jervis

Verified: xcodebuild -scheme Jervis succeeds, produces Jervis.app,
CFBundleName/CFBundleExecutable/CFBundleDisplayName all read "Jervis".
CFBundleIdentifier intentionally stays com.kisani.jarvis (per prior
decision — bundle ID isn't user-facing anywhere including Organizer).

Swift type names (JarvisApp, JarvisWordmark, etc.) and the Gitea repo
name/URL are unchanged — pure internal source identifiers, not user or
developer-facing product identity.

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

project.yml

@@ -1,4 +1,4 @@
-name: Jarvis
+name: Jervis
 options:
   bundleIdPrefix: com.kisani
   deploymentTarget:
@@ -6,14 +6,14 @@ options:
   createIntermediateGroups: true
 
 targets:
-  Jarvis:
+  Jervis:
     type: application
     platform: iOS
     deploymentTarget: "17.0"
     sources:
-      - path: Jarvis
+      - path: Jervis
     info:
-      path: Jarvis/Info.plist
+      path: Jervis/Info.plist
       properties:
         CFBundleDisplayName: Jervis
         CFBundleShortVersionString: $(MARKETING_VERSION)
@@ -39,6 +39,7 @@ targets:
     settings:
       base:
         PRODUCT_BUNDLE_IDENTIFIER: com.kisani.jarvis
+        PRODUCT_NAME: Jervis
         MARKETING_VERSION: "1.0"
         CURRENT_PROJECT_VERSION: "2"
         TARGETED_DEVICE_FAMILY: "1"