feat(SVM): Optimize the sync between sw360 svm

[bibhuti230185]

Optimize the existing SW360-SVM synchronization module by leveraging the modified_after parameter for /public/components and /public/notifications endpoints. This will enable incremental data fetching, reducing the amount of data transferred and improving synchronization efficiency, instead of pulling all data at each sync.

Steps followed and expected result
Current situation: SW360's synchronization with SVM currently pulls all data from /public/components and /public/notifications endpoints during each sync cycle, leading to inefficient data transfer and longer synchronization times.
Expected result: The SW360-SVM synchronization module will be updated to utilize the modified_after parameter available in the /public/components and /public/notifications endpoints. This parameter will be dynamically set to a value representing a recent time window (e.g., the last 2 days from the current sync time), ensuring that only data modified within that period is fetched. This optimization will significantly reduce network load and improve synchronization performance.

Task breakdown

Identify relevant API calls: Locate the existing calls to /public/components and /public/notifications within the SW360 SVM synchronization module.

Implement modified_after logic:

  Develop a mechanism to dynamically calculate the modified_after timestamp (e.g., last sync time minus 1 day). The format should be YYYY-MM-DDTHH:MM:SS.

    
  Integrate this parameter into the API requests for /public/components and /public/notifications.

Handle data merging: Ensure that the incrementally fetched data is correctly merged with the existing data in SW360 without conflicts or data loss.

Error handling: Implement robust error handling for cases where the modified_after parameter might cause issues or if the SVM API behaves unexpectedly with this parameter.

Configuration (Optional): Consider making the "last sync time -N days" configurable for the modified_after parameter.

Issue:

Suggest Reviewer

@GMishx

How To Test?

How should these changes be tested by the reviewer?
Have you implemented any additional tests?

Checklist

Must:

• All related issues are referenced in commit messages and in PR