Move: Filter out usages with visibility error before refactoring

If declaration is already invisible before move,
no visibility conflict should be reported

 #KT-17571 Fixed

idea/testData/refactoring/move/kotlin/moveTopLevelDeclarations/moveClassToPackageWithConflicts/conflicts.txt

@@ -1,4 +0,0 @@
-Class Test uses class Foo which will be inaccessible after move
-Class Test uses function foo(Foo) which will be inaccessible after move
-Method bar() uses class Test which will be inaccessible after move
-Variable t uses class Test which will be inaccessible after move

idea/testData/refactoring/move/kotlin/moveTopLevelDeclarations/moveFunctionToPackageWithConflicts/conflicts.txt

@@ -1,4 +0,0 @@
-Function bar() uses function test() which will be inaccessible after move
-Function test() uses class Foo which will be inaccessible after move
-Function test() uses function foo(Foo) which will be inaccessible after move
-Method bar() uses function test() which will be inaccessible after move

idea/testData/refactoring/move/kotlin/moveTopLevelDeclarations/moveObjectToPackageWithConflicts/conflicts.txt

@@ -1,4 +0,0 @@
-Method bar() uses object Test which will be inaccessible after move
-Object Test uses class Foo which will be inaccessible after move
-Object Test uses function foo(Foo) which will be inaccessible after move
-Variable t uses object Test which will be inaccessible after move

idea/testData/refactoring/move/kotlin/moveTopLevelDeclarations/movePropertyToPackageWithConflicts/conflicts.txt

@@ -1,4 +0,0 @@
-Function bar() uses property test which will be inaccessible after move
-Method bar() uses property test which will be inaccessible after move
-Property test uses class Foo which will be inaccessible after move
-Property test uses function foo(Foo) which will be inaccessible after move