clusterversion: move to 25.4 version

[annrpom]

Checklist:

• Add version key constant for new release (e.g. V24_2), equal to Latest. Note that we do NOT update the PreviousRelease constant. We can only update the PreviousRelease when an RC is published, which is needed for upgrade roachtests.
• Add final version for the previous release (e.g. V24_1).
• Add start version (e.g. V24_2Start with version 24.1-2) and add a new first upgrade for it (in upgrades/upgrades.go).
• Update roachpb.successorSeries map and update TestReleaseSeriesSuccessor
• Update pkg/build/version.txt to the new version (e.g. v24.2.0-alpha.00000000)
• Update the scplan rules in pkg/sql/schemachanger/scplan/internal/rules:
  • copy the contents of current into a new release directory for the previous version (e.g. release_24_1)
  • change package name in all files (including BUILD.bazel), and update the version in current/helpers.go
  • update rulesForReleases in scplan/plan.go
  • rewrite the test outputs: ./dev test pkg/sql/schemachanger/scplan/internal/rules/... --rewrite
  • rewrite TestDeclarativeRules output: ./dev test pkg/cli -f DeclarativeRules --rewrite
• Update releases file: bazel build //pkg/cmd/release:release _bazel/bin/pkg/cmd/release/release_/release update-releases-file Note that the forked release version will disappear from the releases file. This is what we want; if it is here, we will attempt to run upgrade tests against it.
• Regenerate expected test data as needed (usually pkg/sql/catalog/systemschema_test and some logictests).

Epic: REL-2733
Release note: None

[blathers-crl]

Your pull request contains more than 1000 changes. It is strongly encouraged to split big PRs into smaller chunks.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is