fix: don't error out on out-of-sync lock file (#213)

As far as I can see, the `--no-check-lock` argument has been available since Composer 1.0, so adding this argument to the `composer validate` command should be safe and should prevent the issues as reported in #206.

Includes tests (though the test isn't running properly yet).

Fixes #206

Co-authored-by: jrfnl <jrfnl@users.noreply.github.com>

Author: jrfnl

bin/composer_paths.sh

@@ -12,6 +12,7 @@ function validate_composer {
     "${php_path}" "${composer_path}" \
         validate \
         --no-check-publish \
+        --no-check-lock \
         --working-dir "${working_directory}" \
         > /dev/null 2>&1
 }

tests/expect/composer_paths_08.exp

@@ -0,0 +1,17 @@
+#!/usr/bin/env -S expect -f
+
+set timeout 3
+spawn ../../bin/composer_paths.sh "" "../fixtures/out-of-sync-lock"
+match_max 100000
+
+expect "::debug::Composer path is '*'\r
+::debug::Composer version *\r
+::debug::Composer cache directory found at '*'\r
+::debug::File composer.json found at '../fixtures/out-of-sync-lock/composer.json'\r
+::debug::File composer.lock path computed as '../fixtures/out-of-sync-lock/composer.lock'\r
+::set-output name=command::*\r
+::set-output name=cache-dir::*\r
+::set-output name=json::../fixtures/out-of-sync-lock/composer.json\r
+::set-output name=lock::../fixtures/out-of-sync-lock/composer.lock\r
+"
+expect eof

tests/fixtures/out-of-sync-lock/composer.json

@@ -0,0 +1,16 @@
+{
+    "name": "ramsey/composer-install-test-out-of-sync-lock",
+    "description": "Tests composer-install when composer.lock file is out of sync.",
+    "license": "MIT",
+    "authors": [
+        {
+            "name": "Ben Ramsey",
+            "email": "ben@benramsey.com"
+        }
+    ],
+    "config": {
+        "platform": {
+
+        }
+    }
+}