feat(bin-leading-dir): add 'bin-leading-dir' option

[linrongbin16]

Resolve #72 .

This PR add a new option: bin-leading-dir, which allow user customize where to put the bin (e.g. executable binary file(s)) in the archive.

I had explained the idea in https://github.com/taiki-e/upload-rust-binary-action/issues/72#issuecomment-2044396602, also see the README.md changes in this PR

TODO:

• [x] Finish the development.
• [x] Add a new testing matrix for optional arguments. (this PR only add leading-dir and bin-leading-dir, but more like include is possible)
• [x] Pass CI testing.

---

Update: I finished development, and the passed all tests in the CI.

But still, how to verify the built tar.gz and zip packages? to make sure they contains the directory structure as we are expecting?

I try to fork this repo and publish a fork action linrongbin16/upload-rust-binary-action@v1 (https://github.com/marketplace/actions/build-and-upload-rust-binary-to-github-releases-linrongbin16-testing). When using it in another repo, the CI reports v1 is not exist.

[taiki-e]

I try to fork this repo and publish a fork action linrongbin16/upload-rust-binary-action@v1 (https://github.com/marketplace/actions/build-and-upload-rust-binary-to-github-releases-linrongbin16-testing). When using it in another repo, the CI reports v1 is not exist.

Publish to the marketplace is unneeded. You can use your branch: linrongbin16/upload-rust-binary-action@feat-bin-dir

[linrongbin16]

Publish to the marketplace is unneeded. You can use your branch: linrongbin16/upload-rust-binary-action@feat-bin-dir

I tested with this CI (randomly add some combinations on 'leading-dir' and 'bin-leading-dir'):

https://github.com/linrongbin16/cargo-ci-template.rs/blob/cba43840a90f09d6b10dfd0ab56ec7825903c740/.github/workflows/upload-rust-binary-build.yml#L19-L75

and the build assets are:

https://github.com/linrongbin16/cargo-ci-template.rs/releases/tag/v0.4.36

They all look good!

@taiki-e would you take a look?

[taiki-e]

Published in 1.20.0.