[frontend] Refactor Lists to DataTable in every knowledge view

[maelv-filigran]

Use case

The current frontend implementation uses inconsistent List components across different knowledge views in OpenCTI, creating a fragmented user experience. This inconsistency affects user onboarding, introduces potential bugs, and makes code maintenance more difficult. Users encounter different interaction patterns when navigating between various knowledge sections, leading to confusion and reduced efficiency.

Current Workaround

Currently, developers and users work around this by:

• Accepting the inconsistent UI patterns across different knowledge views
• Dealing with the fragmented user experience when navigating between sections
• Managing multiple different List implementations that serve similar purposes
• Spending extra time on bug fixes and maintenance due to code duplication

Proposed Solution

Refactor all List components in knowledge views to use a unified DataTable component. This would:

• Provide a consistent user experience across all knowledge views
• Reduce code duplication and maintenance overhead
• Simplify the onboarding process for new users and developers
• Reduce bug potential by consolidating logic into a single, well-tested component
• Improve the overall UX/UI consistency
• Make the review and merge process more streamlined

Additional Information

Impact: This refactoring affects multiple screens and functionalities across the knowledge management sections of OpenCTI. (screens will be listed)

Benefits:

• Makes onboarding easier for new users
• Reduces bug potential
• Simplifies review/merge process
• Improves UX/UI consistency
• Unifies logic across the application

Estimated effort: Medium-sized task with moderate complexity

Pain Points addressed:

• Outdated patterns
• Unclear logic
• Massive functions

If the feature request is approved, would you be willing to submit a PR?

Yes