feat: replace `docker cp` with a mounted volume in `build`

[EricRibeiro]

Changes

This PR adds support for Windows Hyper-V containers by replacing docker cp with a mounted volume. At the moment, if a user runs the build command on a Hyper-V container, they will receive the following message:

Error response from daemon: filesystem operations against a running Hyper-V container are not supported

With this change, a build folder is created inside the working directory and mounted in the Windows container. While this solves the issue above, it may result in leftover artifacts in non-ephemeral environments if the runner agent is not set to clean up the working directory. Alternatively, users can clean the directory themselves before the end of the workflow.

Checklist

• [x] Read the contribution guide and accept the code of conduct
• [x] Documentation (updated or not needed)
• [x] Tests (added, updated or not needed)

[mishkaechoes]

Thank you for these changes