driver_vive: downgrade unknown lightcap report from error to warning

SV_ERROR with SURVIVE_ERROR_HARWARE_FAULT crashes the process when an
unrecognised USB lightcap report ID is received. New tracker firmware
routinely emits report IDs that older libsurvive versions do not know;
crashing on an unrecognised ID makes libsurvive incompatible with any
firmware newer than it was built against.

The adjacent VIVE_REPORT_USB_TRACKER_LIGHTCAP_V1 case already uses
SV_INFO and ignores the packet. Apply the same treatment to the unknown
case: log a warning and continue so tracking on all known report types
is unaffected.

Author: Mark Stalzer

src/driver_vive.c

@@ -3106,8 +3106,13 @@ void survive_data_cb_locked(uint64_t time_received_us, SurviveUSBInterface *si)
 		} else if (id == VIVE_REPORT_USB_TRACKER_LIGHTCAP_V1) {
 			SV_INFO("USB lightcap report is of an unexpected type for %s: %d (0x%02x)", obj->codename, id, id);
 		} else {
-			SV_ERROR(SURVIVE_ERROR_HARWARE_FAULT, "USB lightcap report is of an unknown type for %s: %d (0x%02x)",
-					 obj->codename, id, id);
+			/* Unknown report IDs are emitted by newer tracker firmware that
+			 * this version of libsurvive doesn't know about. Treating an
+			 * unrecognised ID as a hardware fault is wrong — it crashes the
+			 * process on firmware upgrades. Downgrade to a warning and ignore
+			 * the packet so tracking continues on all known report types. */
+			SV_WARN("USB lightcap report is of an unknown type for %s: %d (0x%02x); ignoring",
+					obj->codename, id, id);
 		}
 
 		break;