fix: resolving rimraf bin dir

[tada5hi]

Description

Due to the fact that rimraf has changed its binary path, lerna no longer works with the new version 4.4.x. Therefore the cli location is now read from the package.json, as fallback the original module resolving was used.

Motivation and Context

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (change that has absolutely no effect on users)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

fixes #3614

[nx-cloud]

Nx Cloud Report

CI is running for commit 1578725.

📂 Click to track the progress, see the status, the terminal output, and the build insights.

---

Sent with 💌 from NxCloud.

[JamesHenry]

Thanks @tada5hi one small change then this LGTM!

[JamesHenry]

Thanks again!

[JamesHenry]

Sadly this didn't actually solve the problem because the bin path is not part of the package's exports and so node blocks it, I am looking into refactoring the whole approach here, I believe we can just use the node API of rimraf instead of all these child process + bin shenanigans

[tada5hi]

damm ... i think the problem is, that i missed to join the pck.bin path with the directory path of require.resolve. Could that be the problem ?

And it should be path.dirname instead of path.basename. I'm really sorry 😔