feat: re-write get all routes to use pagination (#1424)

rewrite get_all routes to use a pagination pattern to allow for better implementations of search, filter, and sorting on the frontend or by any client without fetching all the data. Additionally we added a CI check for running the Nuxt built to confirm that no TS errors were present. Finally, I had to remove the header support for the Shopping lists as the browser caching based off last_updated header was not allowing it to read recent updates due to how we're handling the updated_at property in the database with nested fields. This will have to be looked at in the future to reimplement. I'm unsure how many other routes have a similar issue. 

Co-authored-by: Hayden <64056131+hay-kot@users.noreply.github.com>

mealie/schema/user/user.py

@@ -11,6 +11,7 @@ from mealie.db.models.users import User
 from mealie.schema._mealie import MealieModel
 from mealie.schema.group.group_preferences import ReadGroupPreferences
 from mealie.schema.recipe import RecipeSummary
+from mealie.schema.response.pagination import PaginationBase
 
 from ..recipe import CategoryBase
 
@@ -113,6 +114,10 @@ class UserOut(UserBase):
             }
 
 
+class UserPagination(PaginationBase):
+    items: list[UserOut]
+
+
 class UserFavorites(UserBase):
     favorite_recipes: list[RecipeSummary] = []  # type: ignore
 
@@ -180,6 +185,10 @@ class GroupInDB(UpdateGroup):
         return GroupInDB.get_export_directory(self.id)
 
 
+class GroupPagination(PaginationBase):
+    items: list[GroupInDB]
+
+
 class LongLiveTokenInDB(CreateToken):
     id: int
     user: PrivateUser