[browser] SystemJS_GetLocaleInfo and dependencies

[pavelsavara]

On top of #119866
Just 763ab3c and after

This PR brings interesting question of which final JS module should contain string and memory helpers. They will be used mostly with JS interop, so they would belong to dotnet.runtime.js from that perspective. But this creates dependency arrow in wrong direction. From dotnet.native.js to dotnet.runtime.js, in the case we wanted to make JS interop optional. Adding them as untrimmable closure to dotnet.native.js would solve it.

This is the managed caller

runtime/src/libraries/System.Private.CoreLib/src/System/Globalization/CultureData.Browser.cs

Lines 42 to 50 in f76cbfd

	private unsafe (string, string) JSGetLocaleInfo(string cultureName, string localeName)
	{
	ReadOnlySpan<char> cultureNameSpan = cultureName.AsSpan();
	ReadOnlySpan<char> localeNameSpan = localeName.AsSpan();
	fixed (char* pCultureName = &MemoryMarshal.GetReference(cultureNameSpan))
	fixed (char* pLocaleName = &MemoryMarshal.GetReference(localeNameSpan))
	{
	char* buffer = stackalloc char[LOCALE_INFO_BUFFER_LEN];
	nint exceptionPtr = Interop.JsGlobalization.GetLocaleInfo(pCultureName, cultureNameSpan.Length, pLocaleName, localeNameSpan.Length, buffer, LOCALE_INFO_BUFFER_LEN, out int resultLength);

And maybe we don't need SystemJS_GetLocaleInfo and JSGetNativeDisplayName at all @ilonatommy ?

cc @maraf

[dotnet-policy-service]

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

[radekdoulik]

Suggested change

	export { SystemJS_GetLocaleInfo } from "./globalization-locale";

[pavelsavara]

I solved the problem in #119866