Python: fix nice locations for import aliases

[yoff]

The computation of nice location for import statements did not take aliases into account.
This has causes problems for some of our downstream CI.

See also https://github.com/github/codeql-team/issues/2260

[RasmusWL]

I had to look up what NiceLocationExpr even was, since I had never heard about it before. It seems to only be used in our jump-to-definition queries... although the reason for needing these is a bit obscure to me, it seems to be to ensure spans for things we have definitions for are not overlapping 🤔

For reference, here is how it works for ImportMember:

Using Expr

ImportMember covers whole resource_provider as rp_obj

Using NiceLocaitonExpr

ImportMember only covers rp_obj

[RasmusWL]

Minor suggestion for change note 😊

Did you test out jump-to-def locally before/after changes? (just curious, I think this change is fine to merge evne without doing this)

[RasmusWL]

Suggested change

	* Fixed the computation of display locations for imports with aliases.
	* Fixed the computation of locations for imports with aliases in jump-to-definition.