if pre-release publish with "next" tag on npm instead of default latest

[ashleygwilliams]

per conversation in #1054 (comment)

i apparently misremembered the default behavior of npm pubilsh when you are publishing a package with a semver pre-release version. if something is a pre-release and there are stable releases, we should tag the npm publish as next, not latest. you can see examples of this with prettier and eslint

[gc-victor]

Actually, you can use the pre-release version (ex. pre-release-0.15.0) as a tag, it will be more accurate.