feat: Add incomplete trace detection and adjustable search time offset

[xenonnn4w]

Which problem is this PR solving?

• Resolves Incomplete recent recent traces with elasticsearch backend jaeger#2231

Description of the changes

• Added orphan span detection to identify traces with spans referencing
  non-existent parent spans (indicating potentially incomplete traces)
• Added hasOrphanSpans and orphanSpanCount fields to the Trace type
• Added orange "Incomplete" warning tag in search results for traces with
  orphan spans
• Added warning banner in trace view header for incomplete traces
• Added new search.adjustTime config option that shifts the search end
  time back by a specified duration (e.g., "1m") to exclude very recent
  traces that may still be receiving spans
• UI shows the adjustment suffix in lookback dropdown options (e.g., "Last
  Hour (-1m)")
• Added traceWithOrphans helper in demo trace generators for testing

How was this change tested?

• Added unit tests for orphan span detection in
  transform-trace-data.test.js (5 new tests)
• Added unit tests for applyAdjustTime function in SearchForm.test.js
  (7 new tests)
• Manually verified orphan detection logic via browser console
• Manually verified adjustTime config shows suffix in lookback dropdown
• All existing tests pass

Search Results - Incomplete Trace Warning Tag

Search results showing an incomplete trace with an orange "Incomplete" warning tag.
The tag indicates the trace has spans with missing parent spans, suggesting the trace
may be incomplete due to late-arriving data.

Trace Detail Page - Incomplete Indicator

Trace detail view showing the "Incomplete" indicator inline with the Total Spans
count in the header summary row. The tooltip provides details: "This trace may be
incomplete.

Search Form - Lookback with Time Adjustment Toggle

Search form showing the Lookback field with a time adjustment toggle beside the Lookback(on the right). When adjustTime is configured (e.g., "1m"), a toggle switch appears with the label "Adjusted -1m" and an info icon (?). Clicking the info icon
reveals a popover explaining that when enabled, the search end time is adjusted back by the configured duration to exclude very recent traces that may still be receiving spans. The toggle state is persisted in local storage, allowing users to enable/disable the adjustment as needed.

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[xenonnn4w]

@yurishkuro, may I get your review on this?

[yurishkuro]

• Please provide screenshots indicating the changes
• Please resolve conflicts

[xenonnn4w]

@yurishkuro rebased and updated the pr description with the required screenshots, Thanks!

[yurishkuro]

thanks for the screenshots. I would like two changes:

1. the whole new banner in the trace timeline view is overkill. You can just add an icon with the word "incomplete" in the next row next to the span count. The full text of the banner can go into a tooltip - it's low signal to always show it once the user knows what "incomplete" means.

2. the (-1m) in the time picker is distracting and unnecessary. You can put an info (?) icon next to the word Lookback and explain the -1m offset there.

[xenonnn4w]

@yurishkuro updated the code and screenshots in the description with you requested changes. Thanks.

[yurishkuro]

Can we make "Adjusted -1m" to appear on the same line as Lookback label, only flushed right? The form already has the Go button below the fold on my screen, we don't want to make it longer.

[xenonnn4w]

@yurishkuro updated, Thanks!