feat: add kernelVersion to telemetry traces

[Anirudh2112]

Description

This pull request adds the kernelVersion property to telemetry traces in the TrackTrace method. This enhancement allows pinpointing the specific kernel version responsible for producing logs.

To achieve this:

Introduced a kernelVersionFunc variable to enable easier mocking during tests.
Updated the TrackTrace method to include kernelVersion in telemetry traces.
Added a test (TestTrackTraceIncludesKernelVersion) to verify the inclusion of kernelVersion in trace properties.
Related Issue
This pull request addresses the issue:
#1071

Checklist

I have read the contributing documentation
I signed and signed-off the commits (git commit -S -s ...).
I have tested the changes locally.
I have followed the project's style guidelines.
I have added tests.

Screenshots (if applicable) or Testing Completed

Test Output

The following test passes successfully:

• go test -run TestTrackTraceIncludesKernelVersion

[Anirudh2112]

@microsoft-github-policy-service agree

[Anirudh2112]

Yes, @matmerr that is true, and thank you @rbtr for catching that. I’ve updated the conditional to check for err != nil to avoid infinite recursion. Please let me know if there are any other concerns.

[rbtr]

@Anirudh2112 the infinite recursion is still present, trackWarning calls TrackTrace

[Anirudh2112]

Apologies for the oversight regarding the infinite recursion. In the recent changes, I’ve addressed this by:

1. Replacing the call to t.trackWarning with direct error logging to avoid recursion.
2. Ensuring that errors are logged as separate telemetry traces using appinsights.NewTraceTelemetry.
3. Preserving the original functionality by adding kernelVersion to the properties map when available and maintaining the flow for the main trace.