Remove requirement to supply topic or query to search_memories

[heyitsaamir]

Summary of PR

Previously, topic or query was a requirement for search_memories. But if the dev wants to look at all memories for a user, then this function shouldn't assert this requirement. They may have a good reason to do this (Maybe they want to answer a question using all the previous knowledge of the user)

Details

Testing

Added a unit test

Checklist

• I thought through documentation (and updated the docs if necessary)
• I updated the CHANGELOG.md file (or have a good reason not to)

[Copilot]

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

[singhk97]

They can use the memory_module.get_memories(user_id=user_id) method to get all the memories for a given user.

[heyitsaamir]

They can use the memory_module.get_memories(user_id=user_id) method to get all the memories for a given user.

I know it seems weird to do the same thing in two different ways, but they're for two different purposes. Basically this would make search_memories a superset of get_memories. We could remove get_memories, but it's semantically cleaner for normal CRUD. thoughts?

[singhk97]

They can use the memory_module.get_memories(user_id=user_id) method to get all the memories for a given user.

I know it seems weird to do the same thing in two different ways, but they're for two different purposes. Basically this would make search_memories a superset of get_memories. We could remove get_memories, but it's semantically cleaner for normal CRUD. thoughts?

I'm fine with that. It's simpler from a dev ex perspective as well. I think get_memories still has its place with accepting memory ids as inputs.