Upgrade to React 18

[briangleeson]

Changes

Issue: #3492

• Update to react and react-dom to v18
• Update @tanstack/react-query to 5.90.2
• Update @testing-library/react to 16.3.0
• Add @testing-library/dom to 10.4.1
• Migrate @testing-library/react-hooks support
• Breaking changes in tanstack-query required updates: https://tanstack.com/query/latest/docs/framework/react/guides/migrating-to-v5#the-isdataequal-option-has-been-removed-from-usequery
• Breaking changes in testing-library/react required updates: https://github.com/testing-library/react-hooks-testing-library/blob/chore/migration-guide/MIGRATION_GUIDE.md#waitfornextupdate

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs included if any changes are user facing
• Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[briangleeson]

⚠️ BLOCKER: WebSockets are not working properly for me locally, but I suspect it's some issue within kind/podman/WSL/WIndows that is causing them to break

Using kubectl proxy instead of port forwarding as a workaround works well. Haven't figured out the underlyiung websocket issue though

[briangleeson]

⚠️ Issue in tests: waitForNextUpdate has been removed from testing-library/react. There isn't a direct replacement, and so the two places in the tests that were using it are not fully working with my attempted replacements in src/api/utils.test.js

Solution found and added to tests

[briangleeson]

⚠️ PR checks issue: There's an npm auth failure in the GH Actions workflow for this PR

[briangleeson]

/retest

[briangleeson]

⚠️ PR checks issue: There's an npm auth failure in the GH Actions workflow for this PR

Fixed by latest commit, and rebased with latest

[AlanGreene]

Log requests are duplicated. Each time the step container logs are loaded, 2 requests are made. Previously there was just 1 request.

[briangleeson]

Log requests are duplicated. Each time the step container logs are loaded, 2 requests are made. Previously there was just 1 request.

We determined that this occurs with usage of <StrictMode> wrapper in the app for development mode. It highlights a potential issue of duplicate log fetching requests, due to the lack of an abort handler in the unmount of Log.jsx. But it doesnt have a material impact in local dev env other than duplicate network requests in dev tools, and does not affect production mode. So we are choosing to ignore this for now, as attempting to fix it by adding an AbortController was tricky since Logs. jsx is still a React component using componentDidMount rather than a functional component using useEffect.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AlanGreene

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

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

[AlanGreene]

Thanks @briangleeson. This one wasn't straightforward, so the effort is much appreciated.
/lgtm
/meow

[tekton-robot]

@AlanGreene:

In response to this:

Thanks @briangleeson. This one wasn't straightforward, so the effort is much appreciated.
/lgtm
/meow

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/test-infra repository.