fix: add resource grouping to community node operations and restore 584 community nodes

Community nodes copied from a pre-fix DB had flat operations without resource
grouping. Fixed by:

1. Updating community-node-service.ts extractOperations() to extract resource
   from displayOptions.show.resource (same fix as property-extractor.ts)
2. Re-extracting operations from properties_schema for all 1,396 nodes
3. Restoring 584 community nodes from the n8n 2.13.3 DB snapshot
4. Rebuilding FTS5 index

Result: 366 community nodes now have resource-grouped operations (up from 10).
64 community nodes remain flat (they have no resource/operation pattern).

Conceived by Romuald Członkowski - https://www.aiadvisors.pl/en

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

src/community/community-node-service.ts

@@ -343,10 +343,17 @@ export class CommunityNodeService {
     const operations: any[] = [];
 
     // Check properties for resource/operation pattern
+    // Nodes can have multiple operation properties, each mapped to a resource via displayOptions
     if (nodeDesc.properties) {
       for (const prop of nodeDesc.properties) {
-        if (prop.name === 'operation' && prop.options) {
-          operations.push(...prop.options);
+        if ((prop.name === 'operation' || prop.name === 'action') && prop.options) {
+          const resource = prop.displayOptions?.show?.resource?.[0];
+          for (const op of prop.options) {
+            operations.push({
+              ...op,
+              ...(resource ? { resource } : {})
+            });
+          }
         }
       }
     }