Remove redundant perf client and function wrapper logging

[konstantin-msft]

Remove redundant perf client and function wrapper logging

[Copilot]

Pull Request Overview

This PR removes redundant logging statements from performance client and function wrapper utilities to reduce noise in debug output. The changes focus on eliminating trace-level logging that provides minimal diagnostic value while maintaining error logging and telemetry functionality.

Key changes:

• Removed trace logging from function wrapper execution flow
• Eliminated verbose performance measurement logging from PerformanceClient
• Updated corresponding test expectations to match reduced logging calls

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
lib/msal-common/src/utils/FunctionWrappers.ts	Removed trace logs for function execution start and successful completion
lib/msal-common/src/telemetry/performance/PerformanceClient.ts	Removed trace and info logs for measurement lifecycle events and field updates
lib/msal-common/test/utils/FunctionWrappers.spec.ts	Updated test to reflect reduced logger call count after removing trace statements
lib/msal-browser/src/controllers/StandardController.ts	Improved PKCE code logging message clarity (unrelated cleanup)

Comments suppressed due to low confidence (1)

lib/msal-common/test/utils/FunctionWrappers.spec.ts:66

• The loggerSpy variable is removed but still used in the failure test case on line 94. This will cause a ReferenceError when the test runs.

            const loggerSpy = jest.spyOn(logger, "trace");