release(skeet): avoid saying "release candidate"

There is nothing wrong with release candidates, they are great: Once
enough people have tested a release candidate, it can be confidently
switched to a full release.

So what is wrong about calling Git for Windows' -rc versions (or for
that matter, Git's -rc versions "release candidates" is that, well,
they are _not at all candidates_ to be turned into full releases.

So let's call them what they are: previews.

Signed-off-by: Johannes Schindelin <[email protected]>

Author: dscho

.github/workflows/release-git.yml

@@ -142,7 +142,7 @@ jobs:
             const [, baseVersion, rc ] = ver.match(/^(.*)-rc(\d+)$/) || [ver]
             const skeet =
               rc
-              ? `The ${nth(Number.parseInt(rc) + 1)} release candidate of Git for Windows ${baseVersion} is available, please test! ${releaseURL}`
+              ? `The ${nth(Number.parseInt(rc) + 1)} preview of Git for Windows ${baseVersion} is available, please test! ${releaseURL}`
               : `Git for Windows ${baseVersion} is available! ${releaseURL}`
             const blueskyLink = `https://bsky.app/intent/compose?text=${encodeURIComponent(skeet)}`