feat: extract npm package tars into virtual store as action using tar toolchain from bazel-lib

[gregmagolan]

Should mostly fix #1412. I say mostly since this PR only applies for npm package with no lifecycle hooks and no patches. This is the majority of packages. This PR changes these so they will no longer use a CopyDirectory action with a source directory input to copy into the virtual store. Instead they will use a tar toolchain to extract the package .tgz directly into the virtual store.

Packages with lifecycle hooks and patches will be handled in follow-up PRs. For lifecycle hooks, the lifecycle hook binary will need to run tar --extract itself. This should be fairly straight forward. For packages with patches, we'll likely need a patch toolchain in bazel-lib so we have a hermetic patch we can call after tar --extract in some "extract and patch" action in both npm_package_store and the lifecycle hook binary.

---

Type of change

• New feature or functionality (change which adds functionality)

Test plan

• Covered by existing test cases

[jbedard]

Can tar within _download_and_extract_archive also use the toolchain?

[gregmagolan]

Can tar within _download_and_extract_archive also use the toolchain?

It could but I'd rather change one thing at a time and do that in a follow-up. tar happens to ship on darwin, linux and Windows so its safe to call tar in a repo rule. Not causing any problems in the repo rule atm tho switching to use the toolchain would allow us to remote the _is_gnu_tar check since we pass a gnu tar specific flag to tar --extract.

[jbedard]

It could but I'd rather change one thing at a time and do that in a follow-up.

Yeah 👍

I just want to make sure it's considered because the tar call in _is_gnu_tar is a perf issue on cold builds atm.