[sentry]

When a bulk issue delete or update request contains an invalid search query—for example ?query=issue:155261377 where a numeric group id is passed to the issue: filter instead of a qualified short id—format_search_filter raises an InvalidSearchQuery while building the Snuba query.

Because this happens inside search_fn rather than parse_and_convert_issue_search_query, the exception was not translated to a ValidationError. Both schedule_tasks_to_delete_groups and update_groups_with_search_fn only caught ValidationError, allowing InvalidSearchQuery to bubble up to the top-level endpoint exception handler, which logged an error traceback and returned HTTP 500.

This change:

• Catches InvalidSearchQuery in schedule_tasks_to_delete_groups and returns an HTTP 400 response with {"detail": "Invalid search query."}.
• Catches InvalidSearchQuery in update_groups_with_search_fn and returns an HTTP 400 response with {"detail": "Invalid search query."} without logging an error to Sentry.
• Uses a generic client-safe error message rather than echoing exception internals into the response.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Fixes SENTRY-5Z50

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

[cvxluo]

@sentry get rid of this comment