"Move Field" refactoring causes the assignment statement to change.

When moving the selected field i of class C to class B, before refactoring, j is assigned to 0, and after refactoring, j is assigned to 1.
Code before refactoring:
```java
public class A {
void m(){
int i= 0;
class B {
int j;
void k(){
j= i;
}
}
class C {
B b;
// move 'i' to class 'B'
int i=1;
}
};
}
```
Code after refactoring:
```java
public class A {
void m(){
int i= 0;
class B {
int j;
// move 'i' to class 'B'
int i=1;
void k(){
j= i;
}
}

class C {
B b;
}
};
}

```

Start by reproducing the example through the Java editor's "Move Field" refactoring, using the before-and-after snippets in the issue. Verify that the assignment in B.k() still resolves to the outer i initialized to 0 after moving C.i; the refactoring is done when that behavior is preserved.

Written by the indexing model from the issue text.