fix(api): place AND operator before connector filter in device list

[gustavosbarreto]

Summary

• The connector/platform filter in the device list handler placed the AND operator after the property instead of before
• Since Match processes operators as prefix (applies to the next condition), the platform filter was OR'd with user filters
• This caused WHERE (name ILIKE '%foo%') OR (platform <> 'connector') instead of AND, returning all non-connector devices regardless of the user's search
• Added test that verifies operator ordering and fails without the fix

[github-actions]

Claude finished @gustavosbarreto's task in 2m 29s —— View job

---

Code Review Complete

Reviewed 2 files across code quality, security, testing, Go patterns, and architecture — no issues found. The code looks good as-is.

The fix correctly moves the AND operator before the property filter in both branches of the connector/platform filter logic, ensuring the platform condition is properly AND'd with user filters instead of OR'd. The test effectively validates the ordering invariant by capturing the request and asserting the last two filter elements are [operator(and), property].

---

To request another review round, comment /review.