Use exec in py_binary to avoid child processes

The current approach for the py_binary wrapper means that deployed
instances of py_binary targets create child processes. This can be a
problem when you try to kill the py_binary target since signals and
such don't necessarily get passed along to the child process.

Using the exec functionality here should avoid this particular
problem. The overall behaviour should remain the same.

--
Change-Id: I20ef081e1da5b28a8aff8514d713b1c387ae7f7e
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/4070/
MOS_MIGRATED_REVID=127929454

Author: Philipp Schrader

src/main/java/com/google/devtools/build/lib/bazel/rules/python/stub_template.txt

@@ -109,7 +109,7 @@ def Main():
 
   try:
     sys.stdout.flush()
-    exit(subprocess.call(args))
+    os.execv(args[0], args)
   except EnvironmentError as e:
     # This exception occurs when os.execv() fails for some reason.
     if not getattr(e, 'filename', None):