Invalid query makes graph inaccessible

Nobody has claimed this yet.

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I was trying to reproduce the default queries for tasks (doing & later) and, trying around queries I managed to make the whole graph inaccessible

### Reproduce the Bug

1. Go on test.logseq.com
2. Create a new graph (we're going to break it)
3. Create a query for tasks and add the constraint for it to have something like between and take two random pages
4. Click on the query hashtag
5. Edit the query text to replace the second page in the between query with something invalid like `::today` (note the two dots)
6. Go back to the home
7. Enjoy your broken graph

If you go on the selection of all graphs, it will not work, you need to click on all graph and reload the page

### Expected Behavior

Broken query should not break the whole application

### Screenshots

https://github.com/user-attachments/assets/816f31bc-1832-4e31-abdd-83fc73b8fb65

### Desktop or Mobile Platform Information

_No response_

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Start by reproducing the query described on test.logseq.com: create a graph, use a task query with a between constraint, replace the second page with invalid `::today`, and return home. Observe the query hashtag and all-graphs selection, then trace the query handling involved. Done means the invalid query no longer makes the graph or graph selection inaccessible.

Written by the indexing model from the issue text.