🐛 Bug: aptos-cached-packages writes to cargo home if you use it in your dependencies tree

Right now during build of move packages build directory is created inside of its sources. Imagine adding aptos-cached-packages as your dependency - it ends up modifying cloned sources from git.

This build workflow is not compliant with Cargo. Quoting cargo book:

In general, build scripts should not modify any files outside of OUT_DIR. It may seem fine on the first blush, but it does cause problems when you use such crate as a dependency, because there’s an implicit invariant that sources in .cargo/registry should be immutable. cargo won’t allow such scripts when packaging.

To reproduce

Create new package and add dependency to Cargo.toml:

[dependencies]
aptos-cached-packages = { git = "https://github.com/aptos-labs/aptos-core", tag = "aptos-cli-v3.0.1" }

And run cargo build.

Expected Behavior

Use OUT_DIR for all move packages build artifacts and build files.

System information

Please complete the following information:

• Tag aptos-cli-v3.0.1 but applies to latter

Additional context