'saltbox venv exec' usage not traceable to codebase or generated code

[JeffreyUrban]

The F0cal codebase makes frequent use of saltbox venv exec. Usages are difficult to trace back to code, because stdout/stderr from calling these entrypoints contains only the results of the operation, but no details of what top-level operation is being performed or what generated code is being used.

Troubleshooting such usage regularly devolves to a reverse engineering search effort to discover candidates for what code is behind the output. The included salt steps often provide clues to which top-level operation is being called, but often the same steps are used in multiple entrypoints, leading to the wrong code, or to ambiguity, or the steps are composed of generated code whose source path is indeterminable and whose content is not traceable back to the codebase.

Suggest adding output to all usage of _venv_exec to include the identity of the saltbox function, and the path to any generated code being used, such that all use is traceable to the codebase and to any generated code.

saltbox/src/saltbox/venv.py