There should not be a yarn.lock when building the Docker image of ui-testing for folio-testing.aws since we want the very latest at all times from npm-folioci.
The yarn.lock should be generated and committed for static versions of ui-testing, meant for testing a specific platform build based on released versions only. Once that version of ui-testing is tagged, the yarn.lock should be removed.
However there's a issue with the Docker build trying to move the yarn.lock and failing, because it's not there. Wayne's looking into that.