e2e: avoid redundant labels in JUnit file

Because labels are currently typically added also to the spec texts, we don't
need to write them separately.

This redundancy got introduced in f2cfbf4 when registering all inline tags
also as labels.

Author: pohly

test/e2e/framework/internal/junit/junit.go

@@ -36,6 +36,10 @@ func WriteJUnitReport(report ginkgo.Report, filename string) error {
 		// both, then tools like kettle and spyglass would concatenate
 		// the two strings and thus show duplicated information.
 		OmitFailureMessageAttr: true,
+
+		// All labels are also part of the spec texts in inline [] tags,
+		// so we don't need to write them separately.
+		OmitSpecLabels: true,
 	}
 
 	return reporters.GenerateJUnitReportWithConfig(report, filename, config)