Release 13.2.4, so latest stops being the lowest published version

[MaximBelov]

The published version is 13.2.1-fix.1, which sorts below every other version this fork has on the registry:

13.2.1-fix.1  <  13.2.1  <  13.2.2-dev.0  <  13.2.3-dev.0

So latest points at the oldest of the four, and a consumer with ^13.2.1 resolves to upstream's plain 13.2.1 — a build with none of this fork's changes — rather than to anything published here. ngx-app only escapes that by pinning 13.2.3-dev.0 exactly.

The cause was applying the "upstream's version plus -fix.N" convention without noticing develop had already shipped 13.2.3-dev.0. Worth a caveat in that convention: the suffix has to sort above everything already published, not just above upstream.

What this changes

projects/ng-recaptcha/package.json → 13.2.4. It sorts above everything published so far, carries no prerelease suffix, and lets consumers stop pinning a -dev version exactly.

No library code changes. 13.2.1-fix.1 and 13.2.3-dev.0 are byte-identical apart from README.md and package.json — I unpacked both tarballs and compared all 33 files — so this is a renumbering, not a release of new work. The two -dev versions are left on the registry; nothing should be depending on them.

The root package.json stays at 13.2.1: it is the private workspace (ng-recaptcha-base), never published, so its version carries no consumer-visible meaning.

One thing the README was missing

The "Changes from upstream" list said the fork exists for the npm scope, Angular 18 and the publish workflow — which reads as disposable. It omitted the actual API difference: provideRecaptchaV3Services and provideEnvironmentRecaptchaV3Services do not exist upstream, which exports only RecaptchaV3Module. Verified against the published ng-recaptcha@13.2.1 tarball. ngx-app's login page uses the first of those, so dropping the fork would break it.

Added as a line rather than a rewrite, per the instruction to keep that list current.

After this merges

The publish job will put 13.2.4 on latest. Two follow-ups that need registry access and so cannot be done from here:

• next still points at 13.2.2-dev.0 and will stay there — a develop push now carries the same version as master, so the guard correctly skips it. Moving it needs npm dist-tag add @herdwatch/ng-recaptcha@13.2.4 next.
• Consumers repin from 13.2.3-dev.0 to 13.2.4.

prettier --check passes on the changelog and manifest. README.md was already failing prettier before this change and is left alone apart from the added line, so the one-line addition stays readable in the diff.