`text file busy` when building container entrypoint locally and using restart helper

[lizardruss]

What happened?
On some systems, when running the "hot reload binary" example, users will get a text file busy error when syncing the binary while it's running. This only occurs on some systems. The error is only visible when running with the --debug flag.

What did you expect to happen instead?
Expected the container to restart successfully.

How can we reproduce the bug?

My devspace.yaml, but change the dev.hello-world.command back to /app/server.

Local Environment:

• DevSpace Version: [use devspace --version]
• Operating System: mac
• ARCH of the OS: AMD64

Anything else we need to know?
A workaround is already provided in the repository linked. It simply copies the binary to a location that's not synced and runs the copy. This process could be incorporated into DevSpace somehow.