Update TCK to test for all required REST span properties per semantic…

… conventions 1.19 (#95)

* Specific values of span name is not checked, rather absence of high-cardinality parts of requests
* `net.host.name` and `net.host.port` are required for server Rest spans
* `http.route` is required for server Rest spans
* `net.peer.name` and `net.peer.host` are required for client Rest spans
* error status of span is required for certain 4xx and 5xx requests

Fixes #86, #44

Signed-off-by: Patrik Dudits <patrik.dudits@payara.fish>

tracing/tck/src/main/java/org/eclipse/microprofile/telemetry/tracing/tck/cdi/TracerTest.java

@@ -58,5 +58,6 @@ public static class TracerBean {
         public Tracer getTracer() {
             return tracer;
         }
+
     }
 }

tracing/tck/src/main/java/org/eclipse/microprofile/telemetry/tracing/tck/exporter/InMemorySpanExporter.java

@@ -31,6 +31,7 @@
 import org.awaitility.Awaitility;
 import org.testng.Assert;
 
+import io.opentelemetry.api.trace.SpanKind;
 import io.opentelemetry.sdk.common.CompletableResultCode;
 import io.opentelemetry.sdk.trace.data.SpanData;
 import io.opentelemetry.sdk.trace.export.SpanExporter;
@@ -82,4 +83,9 @@ public CompletableResultCode shutdown() {
         isStopped = true;
         return CompletableResultCode.ofSuccess();
     }
+
+    public SpanData getFirst(SpanKind spanKind) {
+        return finishedSpanItems.stream().filter(span -> span.getKind() == spanKind).findFirst()
+                .orElseThrow(() -> new IllegalStateException("No span found with kind " + spanKind));
+    }
 }