doc: fix LTS replaceme tags
When cherry-picking release commits for LTS releases into master,
the REPLACEME
metadata can be taken over as well, to give users
a more accurate view of what is being released on which release line.
This addresses this problem for all previous LTS releases for which this has not been done.
@nodejs/releasers
Fixes: https://github.com/nodejs/node/issues/33001
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
documentation is changed or added -
commit message follows commit guidelines