Build modules report failed tests through mesh-sdk's failure contract and run its conformance kit (issue 1901)

mesh-build-node kept the first fifteen lines of node --test's output, so a passing line of the first file stood for the
failure. Both build modules now parse through the SDK (go test -json, node --test's TAP report written to a file, the
type-check and go vet as console failures), name themselves in the result, and run the SDK's captured cases; the
catalogue check failurekit refuses a node-build-* module with a test step whose tests do not run the kit.

modules/mesh-build-node/cmd/mesh-build-node/check_test.go

@@ -9,6 +9,7 @@ import (
 	"testing"
 	"time"
 
+	"git.novox.be/novox/mesh-sdk/go/buildstep"
 	"git.novox.be/novox/mesh-sdk/go/forgekey"
 )
 
@@ -198,4 +199,8 @@ func TestTheTestScriptFindsTscAndEsbuildOnItsPath(t *testing.T) {
 	if npm.name != "npm" || !strings.HasPrefix(path, bin+":") {
 		t.Errorf("npm ran with PATH %q, want %s first", path, bin)
 	}
+	// 1901/AC7: the test script runs under node's TAP reporter, written to a file of the workspace the step reads
+	if !slices.Contains(npm.env, "NODE_OPTIONS="+buildstep.NodeTestOptions(filepath.Join(work, "w1", ".mesh-node-test-unit.tap"))) {
+		t.Errorf("npm ran with %v, want NODE_OPTIONS naming the TAP reporter and its file", npm.env)
+	}
 }