fix(exec): passing full path in execv syscall

[miki725]

• [x] Followed the steps in the contributor's guide: https://crashoverride.com/docs/other/contributing#filing-the-pull-request
• [x] PR title uses semantic commit messages
• [x] Filled out the template to a useful degree
• [x] Updated CHANGELOG.md if necessary

Issue

distroless python images break as they are unable to import any deps from the venv

Description

As per execv manpage:

The first argument, by convention, should point to the filename associated with the file being executed.

However it seems like some programs rely on the first argument being absolute path such as in Python sys.executable initialization which changes how its sys.path is filled which in turn impacts its virtual env support.

Now chalk passes the full path which should allow most programs (:fingerscrossed:) to be able to correctly initialize its argv.

Testing

➜ make tests args="test_docker.py::test_distroless --logs"