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/schemas/favorite.py

@@ -11,10 +11,12 @@ class FavoriteResponse(BaseModel):
     id: int = Field(description="Favorite ID")
     user_id: int = Field(description="User ID")
     sound_id: int | None = Field(
-        description="Sound ID if this is a sound favorite", default=None,
+        description="Sound ID if this is a sound favorite",
+        default=None,
     )
     playlist_id: int | None = Field(
-        description="Playlist ID if this is a playlist favorite", default=None,
+        description="Playlist ID if this is a playlist favorite",
+        default=None,
     )
     created_at: datetime = Field(description="Creation timestamp")
     updated_at: datetime = Field(description="Last update timestamp")