Description of problem:

 The FlatpakRemotesPage and RemoteRepositoriesTable components were using custom table implementations instead of leveraging Foreman's standard TableIndexPage component, resulting in inconsistent UX and duplicated code.

How reproducible:

 Always

Is this issue a regression from an earlier version:

 No - this is a code improvement/refactoring

Steps to Reproduce:

1. Navigate to Content > Flatpak Remotes page

2. Examine the table implementation in webpack/scenes/FlatpakRemotes/FlatpakRemotesPage.js

3. Navigate to a specific Flatpak Remote detail page

4. Examine the Remote Repositories table implementation

Actual behavior:
[Describe the issue in detail, including what is happening and where]

Custom table implementations with manual sorting, pagination, and empty state handling. Inconsistent table behavior compared to other Foreman pages. Duplicated code for common table functionality.

Expected behavior:
[Describe what should be happening instead]

Use Foreman's standard TableIndexPage component for consistent UX. Leverage built-in sorting, pagination, search, and empty state handling.

Business Impact / Additional info:

 Code Quality: Reduces technical debt and improves maintainability.
User Experience: Provides consistent table behavior.