Rename breaks at super.fieldName boundary

[lukehutch]

Field renaming breaks at the boundary between a class and its superclass, when the field is defined in the superclass.

Given the following code:

class A {
  final int a;

  A({required this.a});
}

class B extends A {
  final int b;

  B({required super.a, required this.b});
}

class C {
  void c() {
    final a = A(a: 1);
    final b = B(a: 1, b: 2);    // Put cursor here, at 'a'
  }
}

If you click on the indicated a then observe what is highlighted, you see only the a in super.a additionally highlighted:

I would argue that the a in A.a and this.a in class A also should be highlighted.

Now with the cursor in the same location, if you try to rename a to q, the code breaks. This breaks precisely because A.a is not considered to be the same as B.a:

[DanTup]

I don't know if it's the same issue/fix, but occurrences have the same issue here - only the a in class B is highlighted:

[bwilkerson]

@scheglov