fix skeleton server tracing type in accordance with what the server returns -> fixes e2e type checking

Author: MichaelBuessemeyer

frontend/javascripts/test/fixtures/skeletontracing_server_objects.ts

@@ -11,7 +11,6 @@ const TRACING_ID = "skeletonTracingId-47e37793-d0be-4240-a371-87ce68561a13";
 export const tracing: ServerSkeletonTracing = {
   typ: AnnotationLayerEnum.Skeleton,
   id: TRACING_ID,
-  datasetName: "ROI2017_wkw",
   trees: [
     {
       treeId: 2,

frontend/javascripts/test/fixtures/tasktracing_server_objects.ts

@@ -9,7 +9,6 @@ import { ViewModeValues } from "viewer/constants";
 const TRACING_ID = "skeletonTracingId-e90133de-b2db-4912-8261-8b6f84f7edab";
 export const tracing: ServerSkeletonTracing = {
   typ: "Skeleton",
-  datasetName: "ROI2017_wkw",
   trees: [
     {
       nodes: [

frontend/javascripts/test/sagas/proofreading/proofreading_skeleton_test_utils.ts

@@ -112,7 +112,6 @@ export function createSkeletonTracingFromAdjacency(
   };
 
   const tracing: ServerSkeletonTracing = {
-    datasetName: "is-ignored-anyway",
     id: tracingId,
     userBoundingBoxes: [],
     userBoundingBox: undefined,

frontend/javascripts/types/api_types.ts

@@ -953,7 +953,6 @@ export type SkeletonUserState = {
 export type ServerSkeletonTracing = ServerTracingBase & {
   // The following property is added when fetching the
   // tracing from the back-end (by `getTracingForAnnotationType`)
-  datasetName: string; // still part of the proto file, might be outdated. Do not rely on correct values.
   typ: "Skeleton"; // This is done to simplify the selection for the type.
   activeNodeId?: number; // only use as a fallback if userStates is empty
   boundingBox?: BoundingBoxProto;