feat(about): update Node.js release cycle information (#8882)

* content: Update Node.js release cycle information

Clarified the release status of odd and even Node.js versions and updated information on the release cycle starting with Node.js 27.

Signed-off-by: Matt Mayer <152770+matthewmayer@users.noreply.github.com>

* Update previous-releases.mdx

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Signed-off-by: Matt Mayer <152770+matthewmayer@users.noreply.github.com>

---------

Signed-off-by: Matt Mayer <152770+matthewmayer@users.noreply.github.com>
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

Author: matthewmayer

apps/site/pages/en/about/previous-releases.mdx

@@ -8,7 +8,8 @@ layout: about
 <EOLAlertBox />
 
 Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them.
-After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
+Historically (up to Node.js 26), odd-numbered releases (9, 11, etc.) become unsupported after six months, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
+Starting with Node.js 27, the release cycle will be annual and every major version will move to _LTS_ status after its six-month _Current_ phase (and six additional months of _Alpha_ phase).
 _LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
 Production applications should only use _Active LTS_ or _Maintenance LTS_ releases.