report custom go2rtc and ffmpeg builds in analytics (#24928)

Users can swap in their own go2rtc binary at /config/go2rtc or point ffmpeg.path at a custom build, and either can explain stream behavior that looks like a Frigate regression. The install section now reports a custom_go2rtc boolean and an ffmpeg enum (default, bundled, custom) for the configured global path, so no version strings or path text leave the install.

docs/static/frigate-analytics-schema.json

@@ -683,6 +683,15 @@
       "title": "FeaturesSection",
       "type": "object"
     },
+    "FfmpegSource": {
+      "enum": [
+        "default",
+        "bundled",
+        "custom"
+      ],
+      "title": "FfmpegSource",
+      "type": "string"
+    },
     "FpsBucket": {
       "enum": [
         "le_5",
@@ -1017,6 +1026,17 @@
           "description": "CPU architecture",
           "x-public": true
         },
+        "custom_go2rtc": {
+          "description": "Whether an executable /config/go2rtc build exists",
+          "title": "Custom Go2Rtc",
+          "type": "boolean",
+          "x-public": true
+        },
+        "ffmpeg": {
+          "$ref": "#/$defs/FfmpegSource",
+          "description": "Configured global ffmpeg.path: the default build, another bundled version, or a custom path",
+          "x-public": true
+        },
         "image_variant": {
           "$ref": "#/$defs/ImageVariant",
           "description": "Published image the install runs",
@@ -1054,7 +1074,9 @@
         "install_type",
         "arch",
         "kernel",
-        "run_as_root"
+        "run_as_root",
+        "custom_go2rtc",
+        "ffmpeg"
       ],
       "title": "InstallSection",
       "type": "object"