Handle locked cache

[jgsogo]

If something happens during a build, the lock files generated by Conan in the cache will be there and any subsequent conan install will halt forever:

fmt/5.3.0@bincrafters/stable is locked by another concurrent conan process, wait...
If not the case, quit, and do 'conan remove --locks'

We need to handle this situation:

• run conan remove --locks <ref> from time to time? always? <- then we will need to check if there is a running conan install command.
• read the output, detect this line and act
• stop conan install process after a timeout if no output is produced
• ...

[jgsogo]

Add a --non-interactive argument to conan install command so it prints the message and quits?