OU-762: fix flicker on trace detail page

[andreasgerstmayr]

• move @tanstack/query QueryClient higher up the chain to <TracingApp>, to make it usable on every page & to keep the cache
• move useParams() hook in <TraceDetailPage> to a child element; this hook caused re-rendering of the entire <TraceDetailPage> due to https://issues.redhat.com/browse/OCPBUGS-56094

The re-rendering of <TraceDetailPage> every 10-20 seconds caused the cache to be emptied, triggering a re-load of the trace and hence a visible flicker of the Gantt Chart. By restructuring the hooks/elements as above, the trace is not fetched again and there is no flicker.

Resolves: https://issues.redhat.com/browse/OU-762

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-762 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

In response to this:

• move @tanstack/query QueryClient higher up the chain to <TracingApp>, to make it usable on every page & to keep the cache
• move useParams() hook in <TraceDetailPage> to a child element; this hook caused re-rendering of the entire <TraceDetailPage> due to https://issues.redhat.com/browse/OCPBUGS-56094

The re-rendering of <TraceDetailPage> every 10-20 seconds caused the cache to be emptied, triggering a re-load of the trace and hence a visible flicker of the Gantt Chart. By restructuring the hooks/elements as above, the trace is not fetched again and there is no flicker.

Resolves: https://issues.redhat.com/browse/OU-762

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.

[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.

[jgbernalp]

/lgtm
/label ux-approved
no ux changes
/label qe-approved
QE can check post merge with COO

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-762 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

In response to this:

• move @tanstack/query QueryClient higher up the chain to <TracingApp>, to make it usable on every page & to keep the cache
• move useParams() hook in <TraceDetailPage> to a child element; this hook caused re-rendering of the entire <TraceDetailPage> due to https://issues.redhat.com/browse/OCPBUGS-56094

The re-rendering of <TraceDetailPage> every 10-20 seconds caused the cache to be emptied, triggering a re-load of the trace and hence a visible flicker of the Gantt Chart. By restructuring the hooks/elements as above, the trace is not fetched again and there is no flicker.

Resolves: https://issues.redhat.com/browse/OU-762

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.

[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 [jgbernalp]

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