- replace concurrent_check with fuego-specific board lock mechanism
Also, this routine is specific to Jenkins, using a Jenkins CLI url to manage the board status.
'ftc' needs a mechanism to avoid running a test while a Jenkins is job is executing on a board, as well as when ftc is already running a test on a board.
Basically, we need a more global board reservation system, to prevent clashes when running tests on a board (either from Jenkins or from 'ftc').
We might be able to use 'ftc reserve-board' for this (based on old file-based locking done by 'ttc reserve'.