docs(site): add ui-next component documentation and upgrade Docusaurus (#6102)

platform/docs/versioned_docs/version-3.11/migration-guide/3p9-to-3p10/3-UI/1a-Colors.md

@@ -12,7 +12,7 @@ summary: Migration guide for OHIF 3.10's new color system, explaining the transi
 *   **Component Abstraction:** Some styling, especially for interactive elements like buttons, has been abstracted into components (e.g., `ViewportActionButton`, UI library buttons) which use predefined variants (`default`, `secondary`, `ghost`) instead of manual style combinations.
 
 :::note
-You can look at the set of colors in the [Color System](/colors-and-type)
+You can look at the set of colors in the [Color System](/colors-and-theming)
 :::
 
 

platform/docs/versioned_docs/version-3.11/migration-guide/3p9-to-3p10/3-UI/3-Migration-3p10-Input.md

@@ -13,7 +13,7 @@ This guide explains how to migrate from the existing `Input`, `InputNumber`, `In
 
 ## Why Migrate?
 
-  See the full list of components in the [Numeric Component Showcase](/components-list#numeric)
+  See the full list of components in the [Numeric Component](/components/numeric)
 
 
 The old components relied heavily on props, making them complex and difficult to maintain and apply custom styles. The new `Numeric` component provides a structured approach with a context-based API, reducing prop clutter and improving reusability.