Fix TimeZone Names

[tarekgh]

In .NET 8.0 we have done some optimization work to delay initializing the time zone names (Standard, Daylight, and Display names). The reason is the names initialization is extremely expensive especially on non-Windows OS's because we do some heuristics and call ICU to extract such names. Unintentionally doing names lazy initialization on non-Windows OS's caused a problem with the time zones created using Windows Ids e.g. Eastern Standard Time. The reason is to get the correct names of the time zone you need to call ICU using the IANA ids e.g. America/New_York which not done with the lazy initialization. The fix here is to ensure using the IANA ids on non-Windows OS's when requesting the names from ICU.

The repro of the issue, on Linux use code like:

TimeZoneInfo timeZone = TimeZoneInfo.FindSystemTimeZoneById("Eastern Standard Time");
Console.WriteLine($"{zoneName}: {timeZone.Id} ... {timeZone.StandardName} ... {timeZone.DaylightName} ");

This code will display names like GMT which are wrong as expected to show something like Eastern Standard Time: Eastern Standard Time ... Eastern Standard Time ... Eastern Daylight Time.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-datetime
See info in area-owners.md if you want to be subscribed.

[mdh1418]

Looks good to me, thanks!

[tarekgh]

/backport to 8.0-staging

[github-actions]

Started backporting to 8.0-staging: https://github.com/dotnet/runtime/actions/runs/10275576890

[github-actions]

@tarekgh an error occurred while backporting to 8.0-staging, please check the run log for details!

The process '/usr/bin/git' failed with exit code 1