chore(deps): update scalprum dependecies versions

[Hyperkid123]

Description

This is an issue with yarn and how its dependency deduplication works. The problems are exacerbated in mono repositories.

Why was this an issue?

The scallprum test utils package has the following scalprum core version requirement:

"scalprum/core": "^0.6.*"

Ant version 0.*.* is compatible with the packages. However by locking the @scalprum/core dependency to 0.7.0 will result in the following dependency tree in the package:

yarn list --pattern @scalprum/core
yarn list v1.22.19
├─ @scalprum/core@0.6.6
└─ app@1.0.1
   └─ @scalprum/core@0.7.0

I've released versions that strictly require the latest versions of Scalprum. However, this is not an ideal solution. We might have to add yarn resolutions to ensure only actually installed packages is being used. OR switch to npm.

More information about the deduplication issues for nested dependencies can be found here: yarnpkg/yarn#3778

[changeset-bot]

🦋 Changeset detected

Latest commit: 3021d72

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
app	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[sonarcloud]

Quality Gate failed

Failed conditions

3.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[janus-idp]

backstage-showcase Tests on commit 961d7a7 finished with errors.
View test log

[github-actions]

The image is available at: quay.io/janus-idp/backstage-showcase:pr-925!

[gashcrumb]

/lgtm

[Hyperkid123]

@gashcrumb any idea why is the OCP/PR Test failing? I don't have access to the IBM cloud.

[gashcrumb]

Yep, lemme check, though I think at the moment it's expected that they'll fail. I tested this locally and see no problem.

[nickboldt]

This appears to be the opposite of #915 #912

but with an upgrade to "@scalprum/react-test-utils": "0.1.3"

@schultzp2020 @Zaperex

[Zaperex]

I just tested it locally, and it seems to work now. Not sure why the tests e2e-tests are failing at the moment as it seems like it wasn't able to access the UI?

[schultzp2020]

I was told by QE that we can ignore the e2e tests for now. They don't have it fully setup.

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gashcrumb, schultzp2020

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

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