feat(node-workspace): maintain current version range prefix

[OrKoN]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

[OrKoN]

Hey, I have seen #1580 and saw a suggestion to maintain the current range prefix when doing a release. That would work for us in the Puppeteer project (currently, we rely on a custom script to pin dependencies that does not update the changelog). Let me know if you think this approach would make sense and I will look into improving test coverage (hints are welcome).

[danez]

I was just about to start looking into #1580 again and noticed this PR 👍

You can copy the tests from #1580 and modify them slightly.
The current tests should fail anyway and also need probably fixing.

[Daniel950502]

#1749