config: update diagcfg to properly set globalDir

[cce]

Summary

In #6325, the functions exported in logging/telemetry.go were changed from taking a genesisID string argument to configDir/globalDir string argument, and callers are supposed to look up the global configuration directory using config.GetGlobalConfigFileRoot to properly set this argument.

The diagcfg utility was previously passing an empty genesisID argument, and when that became an empty globalDir argument, the effective global configuration file path used inside logging.ReadTelemetryConfigOrDefault was filepath.Join("", TelemetryConfigFilename) which would not read the correct configuration.

[Copilot]

Pull Request Overview

This PR fixes the diagcfg utility to properly read telemetry configuration files after API changes in #6325. The logging/telemetry functions now require a global configuration directory path instead of a genesis ID, and callers must use config.GetGlobalConfigFileRoot() to obtain the correct path.

• Updated function signatures in logging/telemetry.go to use globalDir parameter names consistently
• Modified diagcfg utility to call config.GetGlobalConfigFileRoot() instead of passing empty string
• Added proper error handling for the global directory lookup

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
logging/telemetry.go	Updated parameter names from configDir to globalDir for consistency
cmd/diagcfg/telemetry.go	Fixed telemetry config reading by using proper global directory lookup