K2: Fix incorrect UNRESOLVED_REFERENCE after aliased import in other file

The problem is actually caused by 60f09f6512
It happened because we've been caching package scope using FqName key,
so once one file contains aliased import it would work like other file
contains it, too.

So, the fix is adding excludedNames to the key, too.

^KT-59789 Fixed

compiler/testData/diagnostics/tests/imports/renamedImportInDifferentFile.kt

@@ -1,3 +1,4 @@
+// FIR_IDENTICAL
 // ISSUE: KT-59789
 // FILE: a/A.java
 package a;