Add E2E tests for normalization of version numbers

[AdmiringWorm]

Checklist

• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

In v2.x we introduced version normalization when packaging, installing, upgrading and uninstalling packages (especially in the console output).
However we have missed adding E2E tests (or at least some E2E tests).

Describe The Solution. Why is it needed?

We need to add E2E tests for packaging nuspec files that doesn't already contain a normalized number (both stable and pre-release), when installing an existing package that was created using a non-normalized number (need to test both using the exact version, and the normalized number), upgrading from a non-normalized package and uninstalling a non-normalized package.

The last two may be a bit problematic and needs to be handled manually by copying the required files into the lib directory first.

Additional Context

No response

Related Issues

• Issue Prevent usage of leading 0 in package version numbers #1174

[gep13]

Pushing this issue to the next milestone as it was deemed as not a hard requirement for the 2.0.0 release, but it is something that needs to be done.