fix: add backward compatibility for dependency field is_resolved

fix: add backward compatibility for dependency field is_resolved

- Support both `is_resolved` (legacy) and `is_pinned` (new)
- Mark `is_resolved` as deprecated
- Improve type documentation for clarity

Signed-off-by: Kushal Prasad <your-email@example.com>
Signed-off-by: KUSHAL P <kushalmys55@gmail.com>

Author: kushal-p16

src/services/importedJsonTypes.ts

@@ -201,10 +201,17 @@ export interface Resource {
       is_runtime: boolean;
       is_optional: boolean;
 
-      // ✅ FIX: Support both old and new ScanCode fields
-      is_resolved?: boolean;
+      /**
+       * Indicates whether the dependency is pinned (new field)
+       */
       is_pinned?: boolean;
 
+      /**
+       * @deprecated Use `is_pinned` instead.
+       * Kept for backward compatibility with older ScanCode outputs.
+       */
+      is_resolved?: boolean;
+
       resolved_package: unknown;
       extra_data: unknown;
     }[];