ci: Fix Semantic Versioning For Pre-Release

There is a strict specification for pre-release versions.

Previous template `<mj>.<mn>.<p>-pr<pr>-<run>.0` violated this pattern
and may irritate parsing and ordering semantic versions.

The new template aligns with the standards, so that, for example, a
previous pre-release version:

    16.0.1-pr158-717.0

is now generated as:

    16.0.1-pr.158.717.0

See-also: <https://semver.org/>

.github/workflows/pre-release.yml

@@ -65,11 +65,11 @@ jobs:
           fi
           actual_version=$(cat .release-version)
           prnumber=${{ steps.read-prnumber.outputs.prnumber }}
-          next_version=$(semver --increment prerelease --preid pr${prnumber}-${{ github.run_number }} ${actual_version})
+          next_version=$(semver --increment prerelease --preid pr.${prnumber}.${{ github.run_number }} ${actual_version})
           pnpm run setversion ${next_version} --filter=coremedia/* --dependencyVersion=${next_version}
           pnpm install --no-frozen-lockfile
           git commit -am "Set PR Version: ${next_version}"
-          echo "Chosen Pre-Release Version: ${next_version}"
+          echo "**Pre-Release Version:** ${next_version}" >> $GITHUB_STEP_SUMMARY
       - name: Build
         run: pnpm build
       - name: Lint