[iOS][font] Stop scoping font family name in Expo Go

[tsapeta]

Why

There is no more a reason to scope font family names in Expo Go on iOS. Fonts must be shared between different projects and scoping their names can only cause troubles. In this particular case, because scoped name contains a session ID, the same font loaded by home and NCL would have different font family aliases. As a result NCL is not able to unregister the previous font (from home) to register its own, i.e. it can't get inside this if:

expo/packages/expo-font/ios/FontLoaderModule.swift

Lines 12 to 16 in 739f16d

	// If the font was already registered, unregister it first. Otherwise CTFontManagerRegisterGraphicsFont
	// would fail because of a duplicated font name when the app reloads or someone wants to override a font.
	if let familyName = FontFamilyAliasManager.familyName(forAlias: fontFamilyAlias) {
	try unregisterFont(named: familyName)
	}

How

Modified fontFamilyNeedsScoping function so that it will never return true on iOS. I'm not sure what's the current situation on Android, but maybe we can remove scoping entirely (for sure too late for SDK 51).

Also excluded some tests on iOS that no longer make any sense. Looks like we could remove even more if we do a similar thing on Android (entirely remove describe('within Expo Go'))

To do once this PR is merged: publish dev home

Test Plan

• JS tests are passing
• Fonts and icons load properly in NCL on Expo Go

[reichhartd]

Shouldn't this be imported by expo-modules-core?

[tsapeta]

I think it doesn't matter much as long as we don't need to use properties that are not available in Platform from react-native. I'll change it though, for better consistency. Thanks for pointing this out!