PR: Catch PythonQtError when trying to do alias for QtDataVisualization and dev version correction

[dalthviz]

Fixes #280

[ccordoba12]

Looks good to me, thanks @dalthviz!

[CAM-Gerlach]

FYI @dalthviz , this was milestoned for v1.11.3, but the version attribute was set to 1.12.0...which one did you intend?

[dalthviz]

Hi @CAM-Gerlach 1.12.0.dev0 is the dev version for the branch, on release this will change to be 1.11.3 and then add the end of the release will go back to 1.12.0.dev0 and no further release will be done from that branch (it is a similar approach as the one in Spyder with the 4.x branch where the dev version has the incremented minor i.e 4.3.0.dev0 and the latest release was 4.2.5)

[CAM-Gerlach]

Huh, that wasn't how I remember it used to be with Spyder before. Unless I'm misunderstanding something, its kinda strange to use a dev version that is knowingly higher than the intended release version from the same branch before that version is released, such that the version of the previous dev version will sort higher than the future release version from the same branch, i.e. a current checkout would be considered a later version despite coming before the 1.11.3 release to which it is actually an ancestor. Would seem to violate valid PEP 440 versioning practices, though the impact is limited by the fact that its only a dev version.