Bug: Item pagination on the history page not working

[LuizFNJ]

Background Information

The History page is designed to display a chronological list of events. Currently, the interface is limited to the initial data fetch, with no mechanism to access all records. This prevents users from viewing their full history as the list grows.

Steps to Reproduce

1. Log in to the platform.
2. Navigate to the Histories page.
3. Scroll down to the bottom of the current list.
4. Observe that no "Load More" button or pagination controls are rendered, even when additional records exist in the database.

How

• Frontend: The list component lacks the implementation of a "Load More" trigger or a pagination footer. The conditional rendering for the button might be missing or incorrectly checking the hasMore state.
• Backend/API: Ensure the history endpoint is returning pagination metadata (e.g., totalCount, totalPages, or hasNextPage). If the API doesn't provide this info, the frontend cannot determine if the button should be shown.

Expected Behavior

• A "Load More" button should be visible at the end of the history list if there are more records to fetch.
• Clicking the button should trigger an asynchronous request for the next set of data and append it to the current list.
• The button should be hidden once all available records have been loaded.