e19c6ce23c
In general case, the module where built-ins are looked up (builtInsModule) can have multiple package fragments corresponding to the package "kotlin". Remove the misleading method getBuiltInsPackageFragment along with its implementation details and use the package view's scope instead (by changing KotlinBuiltIns.getBuiltInsPackageScope), since it'll iterate over all fragments accessible in the module and its dependencies. The only difference between scopes of package fragment and package view is that the latter also contains package views for subpackages, which is why the change in BuiltInsReferenceResolverTest is necessary