fix: use canonical project names in API response messages

Use database-retrieved project names (new_project.name, old_project.name)
instead of input parameters (project_data.name, name) in v1 API response
messages to ensure consistent project name casing.

The v2 API already did this correctly. This fixes issue #450 where project
names would display with different casing between add and remove operations.

Fixes #450

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: phernandez <paul@basicmachines.co>

Author: phernandez

src/basic_memory/api/routers/project_router.py

@@ -274,7 +274,7 @@ async def add_project(
             raise HTTPException(status_code=500, detail="Failed to retrieve newly created project")
 
         return ProjectStatusResponse(  # pyright: ignore [reportCallIssue]
-            message=f"Project '{project_data.name}' added successfully",
+            message=f"Project '{new_project.name}' added successfully",
             status="success",
             default=project_data.set_default,
             new_project=ProjectItem(
@@ -329,7 +329,7 @@ async def remove_project(
         await project_service.remove_project(name, delete_notes=delete_notes)
 
         return ProjectStatusResponse(
-            message=f"Project '{name}' removed successfully",
+            message=f"Project '{old_project.name}' removed successfully",
             status="success",
             default=False,
             old_project=ProjectItem(