[3.10-UI] Complete Migration to ohif/ui-next and Deprecation of Legacy OHIF/UI

[sedghi]

To enhance our UI's customization and maintainability, we have released:

• A new playground: https://docs.ohif.org/components
• A Figma kit: https://www.figma.com/community/file/1438619814030377977

In version 3.10, we are working to complete the new components.

Purpose
This update finalizes the migration of the OHIF Viewer’s UI components from the outdated OHIF/UI framework to the new and improved ohif/ui-next. This overhaul is part of a broader effort to enhance the Viewer’s usability, customization, and accessibility, aligning it with modern UI standards. By completing this migration, we’re deprecating the legacy UI framework and fully committing to ohif/ui-next, which leverages the latest advancements from the shadcn/UI and Radix UI libraries.

Why This Matters
The migration to ohif/ui-next brings several benefits to OHIF Viewer users and developers, including:

• Enhanced Customization: The new framework provides more flexible styling options and component configurations, allowing for a more tailored user experience.
• Improved Accessibility: ohif/ui-next components are designed with accessibility in mind
• Full Keyboard Compatibility: All components in ohif/ui-next support keyboard navigation, ensuring a more inclusive experience for users who rely on keyboard-only input.

Key Changes

• Legacy OHIF/UI Deprecation: All remaining legacy components in OHIF/UI will be removed in favor of the new ones in ohif/ui-next.
• Component Mapping & Migration Guide: We’re providing migration guides to help developers map legacy components to their new counterparts in ohif/ui-next, making the transition as smooth as possible.
• Version Release: This migration will be completed in OHIF Viewer version 3.10, building on the initial migration work introduced in version 3.9.

Impact on Users and Developers

• For Users: The Viewer will offer a more modern, accessible, and responsive interface, enhancing the overall experience.
• For Developers: The migration to ohif/ui-next provides a cleaner, more maintainable codebase. Developers will have access to improved documentation and guides, making it easier to build and customize components in the OHIF Viewer.