Prepend directory to the binary tarball

[nibon7]

Description

According to https://www.gnu.org/software/tar/manual/html_section/transform.html, use --transform parameter to prepend directory to each file name.

GNU tar is not available on Mac by default, use a common way.

Closes #6676

Tests

Make sure you've done the following:

• Add tests that cover your changes, either in the command examples, the crate/tests folder, or in the /tests folder.
• Try to think about corner cases and various ways how your changes could break. Cover them with tests.
• If adding tests is not possible, please document in the PR body a minimal example with steps on how to reproduce so one can verify your change works.

Make sure you've run and fixed any issues with these commands:

• cargo fmt --all -- --check to check standard code formatting (cargo fmt --all applies these changes)
• cargo clippy --workspace --features=extra -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect to check that you're using the standard code style
• cargo test --workspace --features=extra to check that all the tests pass

[sholderbach]

Do we have any consumers of our tarballs that might need adjustment with this change?

[nibon7]

Do we have any consumers of our tarballs that might need adjustment with this change?

Nope, as @christianhujer said, the tar archive usually contains a directory.

[sholderbach]

I am wondering if we need to change things for downstream tools or package distributors that download the nu binaries from the GitHub release.
We would have to make sure they can deal with this change correctly (and if they support version pinning to older versions, things don't break with a change to the recipe)

Examples:
https://github.com/Yethal/ansible-role-nushell
https://github.com/marketplace/actions/setup-nu

Dragging in @Yethal and @hustcer for comment

[hustcer]

Setup-nu Action may not work well with the new release workflow, I will test and fix it recently

[Yethal]

No change from my perspective. Ansible role already searches recursively to find the files. With that said, the only reason I'm doing it in the first place is because tarball does not have the directory prepended to it.

[fdncred]

I'm nervous about this one because all downstream consumers might need to change something.

[hustcer]

Feel free to merge this PR, I will fix setup-nu action if it fails for the new release tarball

[Yethal]

@fdncred maybe post about this change on discord/twitter/etc to reach other consumers, other than me and hustcer there are probably people maintaining packages in third party repos such as aur or pacstall

[rgwood]

This seems like a good idea to me.

In general, Linux package managers are going to be building Nu from source and won't be affected by this. Homebrew builds from source too.

[Yethal]

Package managers yes, but places such as pacstall, aur, homebrew etc that automate the process of downloading the release from github might be affected

[rgwood]

Homebrew builds Nu from scratch. I believe AUR does too. I understand that some tools might use our binaries but I suspect the number of such tools is quite small.

[fdncred]

let's move forward with this. I just hope it doesn't come back to bite us on Nov 8th release. Thanks!

[hustcer]

setup-nu@v3 supports latest nu v0.71.0

[rgwood]

Looks like this ended up breaking virtualenv. Hopefully they can work around it. pypa/virtualenv#2442 (comment)