Investigate versioning packages for e2e tests

[vmasek]

As a developer,
I want always be sure I run e2e tests on packages that have been released from my latest code,
to be able to consistently deliver features and fix issues.

The version of package distributed to local (verdaccio) registry could be something specific that is never to be found in released/online (NPM) registry.
For example @development or @e2e or even in combination with random UID/timestamp like @dev-241205_193122 to completely phase out any occurrence of that random behavior that picks up global package or uses inconsistent cashing behaviors