fix dev versions

[bcotrim]

Related issues

• Fixes https://github.com/Automattic/dotcom-forge/issues/10409

The reported issue is caused by an error while parsing the commit hash in the dev builds.
This PR suggest a change that makes dev builds follow a correct versioning convention by using -dev${number} format.
We currently already follow that convention on other builds, for example, -beta1, -beta2, etc...
By using the commit count since the latest release we maintain the ability to track which commit generated that version.

Notes:

• The approval of this PR requires changes in the studio-app/updates endpoint.
• After releasing a version (e.g., 1.3.3), we should immediately update package.json to the next intended version (e.g., 1.3.4). This ensures dev builds are correctly labeled with the version they're working towards (e.g., 1.3.4-dev1) rather than appearing as development builds of the just-released version.

Proposed Changes

• Changed development version format from -dev.HASH to -devN (where N is commit count since last release)
• Updated version counting to use latest release tag (excluding pre-release tags) instead of latest tag
• Added backward compatibility to handle both -dev.HASH and -devN formats
• Updated version handling in build scripts and runtime checks
• Modified artifact naming to use new version format

New dev version on macOS:

New dev version on Windows:

Testing Instructions

1. Test the version generation:

node scripts/prepare-dev-build-version.mjs

2. Check the generated version in package.json:

cat package.json | grep version

3. Test the releases manifest generation:

IS_DEV_BUILD=true node scripts/generate-releases-manifest.mjs

4. Check the releases manifest

cat out/releases.json | jq

5. Test the fastlane distribution (in dry-run mode):

DRY_RUN=true BUILDKITE_BUILD_NUMBER=test-build bundle exec fastlane distribute_dev_build

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?