InternalCommandPortListeningCheck always fails for containers built without `/bin/sh`

Relates to #2984

I'm surprised we've not come across this earlier, but the default TCP port listening detector InternalCommandPortListeningCheck does not work for containers that do not have /bin/sh included.

This predominantly affects images built upon scratch.

The workaround/solution is to use a more application specific WaitStrategy - e.g. an HTTP wait strategy.

However the log messages don't make this easy to realise.

Given that we do both the internal and external port checks for a good reason, I don't think we can just rely on the external port check. Still perhaps we can raise a very specific error message if /bin/sh is not available inside the container.

Commencez par InternalCommandPortListeningCheck et suivez le chemin des logs et des erreurs utilisé lorsqu’un conteneur ne possède pas /bin/sh. Reproduisez le comportement avec une image construite depuis scratch, puis faites en sorte que l’échec identifie clairement le shell manquant et la stratégie d’attente affectée.