UICHKOUT-948: Actions for check out item don't work

[artem-blazhko]

Purpose

By some reason mutator.query.update does not have any impact on current application url.
In the scope of this PR I use history.push instead of mutator.query.update.

Refs

UICHKOUT-948

[github-actions]

Jest Unit Test Results

  1 files  ±0   22 suites  ±0   22s ⏱️ -1s
413 tests ±0  413 ✅ ±0  0 💤 ±0  0 ❌ ±0 
414 runs  ±0  414 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit e7433c1. ± Comparison against base commit 072aeeb.

This pull request removes 3 and adds 3 tests. Note that renamed tests count towards both.

ViewItem component when all data provided should trigger "query.update" for item with correct arguments ‑ ViewItem component when all data provided should trigger "query.update" for item with correct arguments
ViewItem component when all data provided should trigger "query.update" for loan details with correct arguments ‑ ViewItem component when all data provided should trigger "query.update" for loan details with correct arguments
ViewItem component when all data provided should trigger "query.update" for loan policy with correct arguments ‑ ViewItem component when all data provided should trigger "query.update" for loan policy with correct arguments

ViewItem component when all data provided should trigger "history.push" for item with correct arguments ‑ ViewItem component when all data provided should trigger "history.push" for item with correct arguments
ViewItem component when all data provided should trigger "history.push" for loan details with correct arguments ‑ ViewItem component when all data provided should trigger "history.push" for loan details with correct arguments
ViewItem component when all data provided should trigger "history.push" for loan policy with correct arguments ‑ ViewItem component when all data provided should trigger "history.push" for loan policy with correct arguments

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[artem-blazhko]

Problem is not reproducible

[zburke]

@artem-blazhko, It's possible (ahem, **99% likely) that the root cause of this problem, based on the timing of when the ticket was filed and the nature of the bug, was folio-org/stripes-core#1584.

Among other things, PR 1584 refactored from a class-component to a functional one caused a bunch of trouble that we tried to address by putting more things on the dependency array in folio-org/stripes-core#1600. We finally gave up and restored some of the original class-based component in folio-org/stripes-core#1604. Sorry for the trouble!