fix: Ensure group_id consistency for tags/tools

Adds the optional group_id field to RecipeTag and CategoryBase Pydantic
schemas to resolve API validation errors (TypeError/IntegrityError) when
updating recipe tags/categories via PATCH or bulk actions. This ensures
group_id provided in payloads is not stripped during validation.

Also adds the required group_id field to the RecipeToolOut schema.
This ensures group_id is present when validating Recipe objects during
creation in tests, resolving Pydantic validation errors and downstream
IntegrityErrors that occurred during test setup fixtures.

Author: Robert Dana

mealie/schema/recipe/recipe.py

@@ -38,6 +38,7 @@
 
 class RecipeTag(MealieModel):
     id: UUID4 | None = None
+    group_id: UUID4 | None = None
     name: str
     slug: str
 

mealie/schema/recipe/recipe_category.py

@@ -16,6 +16,7 @@ class CategorySave(CategoryIn):
 
 class CategoryBase(CategoryIn):
     id: UUID4
+    group_id: UUID4 | None = None
     slug: str
     model_config = ConfigDict(from_attributes=True)
 

mealie/schema/recipe/recipe_tool.py

@@ -17,6 +17,7 @@ class RecipeToolSave(RecipeToolCreate):
 
 class RecipeToolOut(RecipeToolCreate):
     id: UUID4
+    group_id: UUID4
     slug: str
 
     model_config = ConfigDict(from_attributes=True)