cargo: `cargo package` doesn't include build script if this has a custom path

Problem

One package can have an entry on the manifest indicating a custom path for the build script, for example:

[package]
build = "../folder/build.rs"

Steps

Create a multiple packages that share a single build script and for programmability reasons keep just a single build script

Possible Solution(s)

The expected behaviour in this case would be to ship that build script on the root, and a naive solution would be to modify the behavior of the build attribute to be optional, so in case that the path is not found, default to the root.

The perfect solution would be to modify that entry also on the package, but I don’t know if modification of the manifest is on the philosophy of cargo package

I put the example of ../folder/build.rs because is the worst-case scenario in which the naive solution is clearly naive, since that dir might exist with another context.

Notes

No response

Version

cargo 1.65.0 (4bc8f24d3 2022-10-20)
release: 1.65.0
commit-hash: 4bc8f24d3e899462e43621aab981f6383a370365
commit-date: 2022-10-20
host: x86_64-pc-windows-msvc
libgit2: 1.5.0 (sys:0.15.0 vendored)
libcurl: 7.83.1-DEV (sys:0.4.55+curl-7.83.1 vendored ssl:Schannel)
os: Windows 10.0.19044 (Windows 10 Enterprise LTSC 2021) [64-bit]