[TAPS-425] Improve yarn-install action

[pudek357]

TAPS-425

Description

This PR aims to improve yarn-install action for scenario when there is no occurrence of registry.npmjs.org inside yarn.lock. We have this case in screening-wizard-frontend.

How to test

• Review testing run: https://github.com/toptal/platform/actions/runs/12632044990 (PR with inlining yarn-install into platform to test changes: https://github.com/toptal/platform/pull/80504/files)

Development checks

• Add changeset according to guidelines (if needed)

PR commands

List of available commands:

• @toptal-anvil ping reviewers - Ping teams for review

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5be804c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[ascrazy]

Hi @pudek357,

I ran into the same problem ~2 weeks ago and looking for a resolution came up with idea that we can significantly simplify yarn-install action. Please have a look at this PR #369. Would be cool if you could test it on your use case.

Upd: I have tested #369 on toptal/hire-global and toptal/staff-portal and it works as expected

[denieler]

Haven't tested, by the idea is clear and code looks valid 👍

[pudek357]

Hi @pudek357,

I ran into the same problem ~2 weeks ago and looking for a resolution came up with idea that we can significantly simplify yarn-install action. Please have a look at this PR #369. Would be cool if you could test it on your use case.

Upd: I have tested #369 on toptal/hire-global and toptal/staff-portal and it works as expected

@ascrazy I will answer in #369