When renaming module, ensure rename span is just the last component of the path

[ghost]

Sequel to #24702

Discussed with @mjbvz that editors don't want to handle changing complex paths, but changing just the last component is easier.

[mjbvz]

Does this mean that I can trigger a rename anywhere on an import but that we should only actually rename the last component of the path? Or can I now only trigger a rename on the last component of the path.

In the first case, I believe VS Code will need to know the range of the last component of the path (we could add logic on our side to calculate it too but it would be better if this information came from TS). Adding a renameRange property to the RenameInfo could be useful for other cases too, such as allowing users to rename a class by hitting F2 on the class keyword instead of only on the class symbol name

[ghost]

This PR modifies exactly the property you need, triggerSpan. For some reason it looks like we weren't sending that to you before, fixed by #27160.