AO3-6910 Report Elasticsearch syntax errors to Sentry

[pmonfort]

Pull Request Checklist

• Have you read the contributing guidelines?
• Have you read "How to write the perfect pull request"?
• Have you added tests for any changed functionality?
• Have you added the Jira issue number as the first thing in your pull request title (e.g. AO3-1234 Fix thing)
• Do you have fewer than 5 pull requests already open? If not, please wait until they are reviewed and merged before creating new pull requests.
• I acknowledge that submitting code created or modified with the help of AI is a bannable offense.

Issue

https://otwarchive.atlassian.net/browse/AO3-6910

Purpose

When an Elasticsearch BadRequest error occurs (e.g. from a search syntax error), the exception is rescued and a user-facing banner is shown, but nothing is reported to Sentry. This makes it difficult to debug what caused the error.

This PR adds Sentry.capture_exception calls in the two places where Elastic::Transport::Transport::Errors::BadRequest is rescued:

• Query#search the main search path (works, bookmarks, tags, etc.)
• AutocompleteController#noncanonical_tag noncanonical tag autocomplete

Both use if defined?(Sentry) since the Sentry gems are only loaded in staging/production.

Testing Instructions

1. Go to https://archiveofourown.org/works?work_search[sort_column]=null&work_search[other_tag_names]=null&work_search[excluded_tag_names]=null&work_search[crossover]=null&work_search[complete]=null&work_search[words_from]=null&work_search[words_to]=null&work_search[date_from]=null&work_search[date_to]=null&work_search[query]=null&work_search[language_id]=null&commit=Sort%20and%20Filter&tag_id=Older%20Man*s*Younger%20Woman&page=2
2. Verify the user still sees the syntax error banner
3. Ask a Systems or Senior AD&T member to check Sentry for the new Elassport::Errors::BadRequest issue

Credit

Pablo Monfort (he/him)