Feat support bun pack

[Jordan-Hall]

Current Behavior
Before release last night/today of bun 1.1.27 bun pm pack didn't exists so we fell upon npm pack.

Expected Behavior
If bun 1.1.27 or greater we use bun pm pack otherwise we revert to npm pack

https://x.com/bunjavascript/status/1832386689182122092

cc: @jaysoo

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Dec 19, 2024 3:57pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 524a878.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	43m 35s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	1m 40s	View ↗
nx-cloud record -- nx format:check --base=39b8a...	✅ Succeeded	2m 4s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	27s	View ↗
nx documentation --no-dte	✅ Succeeded	1m 13s	View ↗
nx affected -t e2e-macos-local --parallel=1 --b...	✅ Succeeded	24m 19s	View ↗

---

☁️ Nx Cloud last updated this comment at 2024-12-19 16:41:50 UTC

[leosvelperez]

Thanks for the contribution!

Unfortunately, bun pm pack creates a tarball of the current workspace (similar to yarn), which is not what the current packageRegistryPack helper function is intended to do. That helper function is intended to produce a tarball of packages retrieved from the registry.

I'm closing this since the changes wouldn't produce the desired result.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.