False negative: missing os.exec* APIs with `sh -c` as sink in py/code-injection.

**Description of the issue**

py/code-injection flags command injection when the code uses os.system(...) or subprocess.run(..., shell=True), but it does not flag the same tainted command when it is executed through Python os.exec* APIs with sh -c.

A minimal example:
```python
files = request.args.get("files", "")
os.execl("/bin/sh", "sh", "-c", "ls " + files)
```

I also tested equivalent variants (os.execlp, os.execve, and subprocess.run(["sh","-c", ...])) and they were not reported either, while the os.system and shell=True controls were reported.

Sink pattern example in the wild:
https://github.com/ziyan/ssh-otp/blob/ad23edded03ee7d198417d99457d3cfa3df814d1/ssh-otp#L90
There are also code using `python -c
https://github.com/davidfraser/dbghelper/blob/f12b91b468bb640f1cb9d19733afef7696eee9fa/dbg.py#L47

Commencez par la requête py/code-injection et comparez sa gestion existante des sinks os.system et subprocess.run(shell=True) avec l’exemple os.execl signalé. Exécutez l’exemple minimal et les variantes équivalentes, puis vérifiez que les commandes contaminées transmises via sh -c sont signalées, tandis que les contrôles existants restent couverts.

Rédigé par le modèle d'indexation à partir du texte de l'issue.