chore: [release-1.8] partial fix for tar

[kim-tsao]

Description

Partial updates for tar:

• Includes patches from closed PR.
• Add a resolution for tar versions (^6.1.12) specific to the patches since we cannot apply patches to a nested dependency of a patch. This will ensure we are selectively updating the correct versions
• Add a resolution in the dynamic-plugins/yarn.lock to force the kubernetes/client-node v0.20.0 to v0.22.3. This dependency is only used in @backstage/backend-common which is a dependency of the roadiehq/scaffolder-backend-argocd plugin. It was removed in subsequent versions of the plugin with no code changes which indicates that it was an unused dependency. Kube client v0.22.3 has patched versions of jsonpath-plus and tar v7.

Please explain the changes you made here.

Which issue(s) does this PR fix

• Fixes #?

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[github-actions]

The container image build workflow finished with status: failure.

[github-actions]

The container image build workflow finished with status: cancelled.

[github-actions]

The container image build workflow finished with status: failure.

[github-actions]

The container image build workflow finished with status: failure.

[github-actions]

The container image build workflow finished with status: failure.

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

[openshift-ci]

PR needs rebase.

Details

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.