fix(pipecat): use client.add, memories.add was removed in supermemory 3.x

[Cintu07]

supermemory_pipecat stores messages with client.memories.add(...), but
.add was moved off memories to the top level (client.add(...)) in
supermemory 3.x. the package pins supermemory>=3.16.0, a range where
memories.add no longer exists, so a fresh install pulls 3.51 and every
store raises AttributeError.

it's worse than a hard crash: the call sits in a fire-and-forget block that
only logs the error (service.py _store_messages), so memory silently never
gets stored and the user never sees why.

fix is one line: call client.add(**add_params). confirmed the top-level
add accepts the same params this passes (content, container_tags, custom_id,
metadata), and that client.memories.add is gone on current supermemory ^^

[Copilot]

Pull request overview

Fixes the supermemory_pipecat Python integration to match Supermemory 3.x’s client API by using the top-level client.add(...) method instead of the removed client.memories.add(...), preventing silent failures in the fire-and-forget message storage path.

Changes:

• Update _store_messages to call await self._supermemory_client.add(**add_params) for Supermemory 3.x compatibility.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Cintu07]

same root cause as #1236 (supermemory 3.x moved .add off .memories), just in
a different sdk. that one's an install-time cap, this one's a runtime call
that fails silently. this is very small and independent fix. so yeah

[Cintu07]

this fixes a silent bug: pipecat stores with client.memories.add, which supermemory 3.x removed, so every save quietly fails inside the fire-and-forget block and the user never sees it. one line fix to client.add.

also added the regression test copilot suggested: it asserts _store_messages calls client.add and not the old memories.add, so this cannot silently break again. both tests pass.

the bug is still on main and this has only had the bot look at it so far. mind giving it a review when you get a sec @ishaanxgupta?