BDMS-764: Add contact name & type to water well list search

[TylerAdamMartinez]

Why

This PR addresses the following problem/context:

• Search functionality was limited to name_contains, restricting users to exact/partial name matches only
• Users could not effectively search by other attributes, such as thing type or related contact names
• The existing search did not handle typos or approximate matches (e.g., “Aron” vs “Aaron”)
• This limited usability and made it difficult to locate relevant records

How

Implementation summary - the following was changed/added/removed:

• Replaced name_contains parameter with a unified query parameter across the frontend and backend
• Implemented a combined search strategy in get_db_things():
  • Full-text search using Thing.search_vector (tsvector)
  • Fuzzy matching using PostgreSQL pg_trgm (% operator)
  • Added similarity-based ranking using similarity() to improve result ordering

Notes

Any special considerations, workarounds, or follow-up work to note?

• Requires PostgreSQL pg_trgm extension to be enabled for fuzzy search
• Search behavior now depends on both search_vector configuration and trigram matching
• Contact search is only applied when include_contacts=true to avoid unnecessary joins

[jacob-a-brown]

Should the query be sanitized to prevent malicious behavior?

[TylerAdamMartinez]

Should the query be sanitized to prevent malicious behavior?

Yes, good point. I double-checked that there is nowhere in this code change where a user query parameter is placed directly into an SQL statement.

[TylerAdamMartinez]

Grabacion.de.pantalla.2026-05-04.a.la.s.13.24.30.mov

[ksmuczynski]

Are these changes carried over into the Docker setup, too?