NO-JIRA: Do not fetch filter bar values on every re-render, and prevent flicker

[andreasgerstmayr]

• use absoluteTimeRange from TimeRangeProvider, which keeps the absolute time range during re-renders. Previously, I calculated the absolute time range from the relative time range (e.g. "last 30 minutes") on every re-render, which resulted in a network request on every re-render
• refresh the absolute time range on every query change also in the filter bar
• do not fetch search results twice when navigating back from the gantt chart to the search

[openshift-ci-robot]

@andreasgerstmayr: This pull request explicitly references no jira issue.

In response to this:

• use absoluteTimeRange from TimeRangeProvider, which keeps the absolute time range during re-renders. Previously, I calculated the absolute time range from the relative time range (e.g. "last 30 minutes") on every re-render, which resulted in a network request on every re-render
• refresh the absolute time range on every query change also in the filter bar

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[andreasgerstmayr]

/label ux-approved
minimal UX changes

[jgbernalp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreasgerstmayr, jgbernalp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andreasgerstmayr,jgbernalp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[IshwarKanse]

/label qe-approved

[openshift-ci]

@andreasgerstmayr: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.