[APM] Default time range overrides fetched range for link-to/trace URLs without range parameters

[ryanrupp]

See forum post here for more context.

Kibana version:
7.15.0

Elasticsearch version:
7.15.0

Server OS version:
Ubuntu 20.04

Browser version:
OSX Chrome

Browser OS version:
93.0.4577.82

Original install method (e.g. download page, yum, from source, etc.):
Docker

Describe the bug:
In 7.12.1 I had setup trace.id field to link to the APM page via apm#/link-to/trace/{{value}} - this worked correctly and when you opened the page it would open the root transaction and narrow the date range filter around the time of the transaction.

After upgrading to 7.15.0, linking to traces that are older than 15 minutes fails to work. I noticed the date range is set to from: now-15m, to: now which I think is the issue even though the API call to look up transaction_root works it fails to render the transaction due to it not being within the date range. I believe this is due to the change here where a default time range is now being used paired with the link builder here gives precedence over the rangeFrom input over transaction.timestamp.

As a temporary workaround if I change the field URL template to:

apm#/link-to/trace/{{value}}?rangeFrom=now-7d

I can continue to view the trace provided the trace occurred within the last 7 days.

Steps to reproduce:

1. Find a trace that occurred over 15 minutes ago
2. Take the trace ID and navigate to /app/apm#/link-to/trace/{{traceId}}

Expected behavior:
The trace opens in the transactions view with the date range of the transaction focused.

[ryanrupp]

Relates to change in #108777

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[dgieselaar]

Should be as "easy" as removing the default query parameters for the link-to/trace route.