Refactor user endpoint tests to include pagination and response structure validation

- Updated tests for listing users to validate pagination and response format.
- Changed mock return values to include total count and pagination details.
- Refactored user creation mocks for clarity and consistency.
- Enhanced assertions to check for presence of pagination fields in responses.
- Adjusted test cases for user retrieval and updates to ensure proper handling of user data.
- Improved readability by restructuring mock definitions and assertions across various test files.

app/repositories/favorite.py

@@ -118,7 +118,9 @@ class FavoriteRepository(BaseRepository[Favorite]):
             raise
 
     async def get_by_user_and_sound(
-        self, user_id: int, sound_id: int,
+        self,
+        user_id: int,
+        sound_id: int,
     ) -> Favorite | None:
         """Get a favorite by user and sound.
 
@@ -138,12 +140,16 @@ class FavoriteRepository(BaseRepository[Favorite]):
             return result.first()
         except Exception:
             logger.exception(
-                "Failed to get favorite for user %s and sound %s", user_id, sound_id,
+                "Failed to get favorite for user %s and sound %s",
+                user_id,
+                sound_id,
             )
             raise
 
     async def get_by_user_and_playlist(
-        self, user_id: int, playlist_id: int,
+        self,
+        user_id: int,
+        playlist_id: int,
     ) -> Favorite | None:
         """Get a favorite by user and playlist.