fix: accept top-level temporal query filters

[haosenwang1018]

Summary

• make /memory/query accept top-level startTime and endTime request fields in addition to the nested filters form
• update the shared q_req type so the route implementation and request shape stay in sync

Why

Issue #105 reports that temporal filtering is ignored for /query-style requests like:

{"query":"text","startTime":9999999999999}

The root cause is that /memory/query only read:

• filters.startTime
• filters.endTime

So top-level temporal fields were silently ignored, even though another query entrypoint (/query in routes/vercel.ts) already accepts the top-level form.

This patch makes the main /memory/query route honor the same top-level temporal filters, which matches the reported reproduction and keeps both query entrypoints consistent.

Testing

• cd packages/openmemory-js && npm run build

Closes #105

[nullure]

LGTM