Sovler-based cursor info is reporting refactorings that aren’t applicable with AST-based refactoring implementation

[ahoppen]

The solver-based cursor info reports rename refactorings based on whether it resolved the current item. But since the refactoring itself uses the AST-based implementation the refactoring might not actually be applicable. We probably need to still run the AST-based implementation for cursor info to tell if rename is actually available.

The proper solution here would probably be to create two requests: One that just returns the cursor info and another one that returns the available refactorings. The latter could then use the AST-based implementation while the former is purely solver-based.

[ahoppen]

The local refactoring action has been removed but the underlying issue probably still persists when getting local rename ranges.