Turn derivation unit tests into unit characterization tests

The brings a number of advantages, including:

- Easier to update test data if design changes (and I do think our
  derivation JSON is not yet complaint with the guidelines).

- Easier to reuse test data in other implementations, inching closer to
  compliance tests for Nix *the concept* rather than any one
  implementation.

src/libstore/tests/protocol.hh

@@ -29,7 +29,7 @@ public:
     {
         if (testAccept())
         {
-            GTEST_SKIP() << "Cannot read golden master because another test is also updating it";
+            GTEST_SKIP() << cannotReadGoldenMaster;
         }
         else
         {
@@ -70,7 +70,7 @@ public:
         {
             createDirs(dirOf(file));
             writeFile(file, to.s);
-            GTEST_SKIP() << "Updating golden master";
+            GTEST_SKIP() << updatingGoldenMaster;
         }
         else
         {