Description

In the explore view, the input field accept either a TraceQL query or a Trace ID, and displays the trace table or the Gantt chart based on the value. Unfortunately, the lezer grammar (correctly) marks Trace IDs as invalid TraceQL queries. Therefore, let's disable syntax highlighting if the input is a Trace ID.

Screenshots

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.
• Visual tests are stable and unlikely to be flaky.
  See Storybook
  and e2e docs for more details. Common issues
  include:
  • Is the data inconsistent? You need to mock API requests.
  • Does the time change? You need to use consistent time values or mock time utilities.
  • Does it have loading states? You need to wait for loading to complete.