CTONET-986: Support for our own results stream and unique identifiers

This change does the following:
1) Modifies the claim.schema.json to support a generic "identifier", composed
   of a "url" and "version".
2) Modifies the claim.schema.json to support a generic "result", composed of
   the JUnit metadata that we are require, and in the format we desire.
3) Modifies claim.schema.json to become more accepting to "configuration".  The
   downstream patch here:

   https://github.com/test-network-function/test-network-function/commit/ \
   54b0ba6e82ef6e46efc8ccbf0f5de07de7936e2d#diff- \
   a3d824da3c42420cd5cbb0a4a2c0e7b5bfddd819652788a0596d195dc6e31fa5

   started to use arrays instead of maps to represent config objects, which in
   turn violated the schema here.  Since we no longer have expectations of a
   map here, I also removed the override in overrides.json.
4) Changes "results" -> "rawResults".  Puts our "pretty" results in "results".
5) Regenerates the golang client based on the updated claim.schema.json.
6) Adds a significant number of tests, and modifies old ones, to comply with
   the new schema.

This is the building block for the downstream adoption of the schema changes,
and enhanced reporting capabilities.

Signed-off-by: Ryan Goulding <[email protected]>

Author: ryandgoulding

override.json

@@ -3,13 +3,13 @@
     {
       "path": [
         "claim",
-        "configurations"
+        "nodes"
       ],
       "overrideType": "map[string]interface{}"
     }, {
       "path": [
         "claim",
-        "nodes"
+        "rawResults"
       ],
       "overrideType": "map[string]interface{}"
     }, {