Revert #23583: Ineffective TypeScript type handling in telemetry utils (

#23615)

The changes in #23583 for handling record access in telemetry utils
didn't achieve the intended type safety improvements. While they
satisfied linter rules, TypeScript still ignores `undefined`
possibilities, leaving type analysis in these situations potentially
untested.

packages/utils/telemetry-utils/src/mockLogger.ts

@@ -7,7 +7,6 @@ import {
 	type ITelemetryBaseEvent,
 	type ITelemetryBaseLogger,
 	LogLevel,
-	type Tagged,
 } from "@fluidframework/core-interfaces";
 import { assert } from "@fluidframework/core-utils/internal";
 
@@ -16,7 +15,6 @@ import type {
 	ITelemetryEventExt,
 	ITelemetryLoggerExt,
 	ITelemetryPropertiesExt,
-	TelemetryEventPropertyTypeExt,
 } from "./telemetryTypes.js";
 
 /**
@@ -332,10 +330,7 @@ function matchObjects(
 	expected: ITelemetryPropertiesExt,
 ): boolean {
 	for (const [expectedKey, expectedValue] of Object.entries(expected)) {
-		const actualValue:
-			| TelemetryEventPropertyTypeExt
-			| Tagged<TelemetryEventPropertyTypeExt>
-			| undefined = actual[expectedKey];
+		const actualValue = actual[expectedKey];
 		if (
 			!Array.isArray(expectedValue) &&
 			expectedValue !== null &&

packages/utils/telemetry-utils/src/test/errorLogging.spec.ts

@@ -689,7 +689,7 @@ const annotationCases: Record<string, IFluidErrorAnnotations> = {
 describe("normalizeError", () => {
 	describe("Valid Errors (Legacy and Current)", () => {
 		for (const annotationCase of Object.keys(annotationCases)) {
-			const annotations: IFluidErrorAnnotations | undefined = annotationCases[annotationCase];
+			const annotations = annotationCases[annotationCase];
 			it(`Valid Fluid Error - untouched (annotations: ${annotationCase})`, () => {
 				// Arrange
 				const fluidError = new TestFluidError({ errorType: "et1", message: "m1" });