feat: add IS NOT NULL operator to query builder

[LakshmiSravyaVedantham]

Summary

• Adds IS_NOT_NULL = "IS NOT NULL" to the Operator enum
• Updates _build_where_query() to handle unary operators that don't require a literal or expression argument
• Enables usage: where(item='n.name', operator=Operator.IS_NOT_NULL) → WHERE n.name IS NOT NULL

Closes #293

Test plan

• match().node(variable='n').to().node(variable='m').where(item='n.name', operator=Operator.IS_NOT_NULL).return_() should produce MATCH (n)-[]->(m) WHERE n.name IS NOT NULL RETURN *;
• Existing where() calls with literal/expression should continue working unchanged

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

lakshmisravya123 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[antejavor]

Hi @LakshmiSravyaVedantham, thanks for the contribution. Can you sign the CLA?

[antejavor]

Let's just drop the comment and a test for this PR, CI passes and if we merge 🦾

[antejavor]

Suggested change

# Unary operators (e.g., IS NOT NULL) don't require a literal or expression