Add valid release examples to releases documentation

[JoshFerge]

Which part? Which one?

Improve Release Semver documentation

Description

On our releases pages, we give a grammar of what a valid release is, but don't give concrete examples of various values that users can set.

Suggested Solution

It would be nice if we could include these values:

  - Examples of valid Semver releases:
      "package@1",  # Major version only
      "package@1.0",  # Major and minor version
      "package@1.0.0",  # Major, minor, and patch version
      "package@1.0.0-alpha",  # With prerelease
      "package@1.0.0-alpha.1",  # With prerelease and number
      "package@1.0.0-alpha.beta",  # With prerelease and text
      "package@1.0.0-rc.1+43",  # With prerelease and build
      "package@1-alpha+43",  # major only with prerelease and build
      "org.example.FooApp@1.0+whatever",  # With build metadata
      "package@1.0.0.1",  # Four version components with revision (major.minor.patch.revision)
      "package@1.0.0-alpha.1.2",  # pre-release
      "package@1.0.0-beta+exp.sha.5114f85",  # pre-release and build
      "package@1.0.0+20130313144700",  # version and build
      "package@1.0.0-0.3.7",  # Prerelease starting with number
      "package@1.0.0.0-beta+exp.sha.5114f85",  # major, minor, patch, revision, pre-release, and build

They would go here, for example: https://docs.sentry.io/platforms/javascript/guides/astro/configuration/releases/#bind-the-version

after the last Semantic bullet, still under the Semantic bullet list. There are a bunch of release.mdx files where we need to insert these and make sure it's formatted correctly and looks good.

[linear]

DOCS-2208 Add valid release examples to releases documentation