fix: replace crypto.randomUUID with fallback for non-HTTPS contexts

crypto.randomUUID() requires a secure context (HTTPS). Since the server
may be accessed via HTTP, use a timestamp + random string ID instead.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

ui/src/pages/Routes/RouteDetail.tsx

@@ -521,7 +521,7 @@ export default function RouteDetail() {
   function saveTap() {
     if (!config.data) return;
     const tap: TapDefinition = {
-      tapId: editingTap?.tapId || crypto.randomUUID(),
+      tapId: editingTap?.tapId || `tap-${Date.now()}-${Math.random().toString(36).slice(2, 10)}`,
       processorId: tapProcessor,
       target: tapTarget,
       expression: tapExpression,