♻️(frontend) decouple PaginationControl from usePagination hook

Replace ReturnType<typeof usePagination> prop type with explicit Props
interface defining only required fields (currentPage, totalPages,
onPageChange) to decouple component from internal hook implementation.

Eliminates unnecessary runtime dependency and improves component API
clarity by explicitly declaring required props instead of coupling to
hook internals, making the component more maintainable and reusable.

src/frontend/src/features/rooms/livekit/components/controls/PaginationControl.tsx

@@ -1,19 +1,16 @@
 import * as React from 'react'
 import { createInteractingObservable } from '@livekit/components-core'
-import { usePagination } from '@livekit/components-react'
 import { RiArrowLeftSLine, RiArrowRightSLine } from '@remixicon/react'
 import { Button } from '@/primitives'
 import { useEffect, useState } from 'react'
 import { useTranslation } from 'react-i18next'
 import { css } from '@/styled-system/css'
 
-export interface PaginationControlProps
-  extends Pick<
-    ReturnType<typeof usePagination>,
-    'totalPageCount' | 'nextPage' | 'prevPage' | 'currentPage'
-  > {
-  /** Reference to an HTML element that holds the pages, while interacting (`mouseover`)
-   *  with it, the pagination controls will appear for a while. */
+export interface PaginationControlProps {
+  totalPageCount: number
+  nextPage: () => void
+  prevPage: () => void
+  currentPage: number
   pagesContainer?: React.RefObject<HTMLElement>
 }