Re-integrate Sentry's Session Replay to the Website

I believe Session Replays provided valuable information on what users are doing, and I think it is worth to re-add Sentry on the Website, even if it is just for Session Replay.

It needs to be done in a way that it bootstraps in a separate chunk and after page-load, we can't have user experience being affected by this + I'm fine only integrating Session Replay and nothing more.

I want to better understand how many users are going to the ESP/EOL page in Node.js Releasdes + what download options people are choosing. We might update the Dropdown of download options to give unique classnames or IDs btw.

One of the reasons are that the DevBox option on Downloads is scratching my head. I've never seen anyone using this option (in the sense that I don't know anyone that uses DevBox) and I do believe we should have some criteria or say on what should be added there even if it passes all community critera.

Better understanding the numbers will provide a better case to add part of the community criteria something like "the community critera needs to pass at leasy lazy-consensus when requested to be added through an issue; and any website team member can raise an issue to remove it at any given time at their discretion if it passes also the consensus seeking process" -- for me this is a path to protect ourselves from overbloating the download dropdown options + from edge cases that could misleadingly be passing all communinity criteria (not official ones, although IMO official ones should ALSO be approved by a consensus seeking process)

I'm fine proposing an amend to that. As @ljharb said once, we should avoid bloating the dropdown with whatever that appears. This is a way to protect ourselves in a democratic manner.

cc @nodejs/nodejs-website @nodejs/web-infra

Comienza por los puntos de entrada del sitio web para la página de ESP/EOL y la página de Downloads, especialmente el download-options dropdown. Revisa cómo se integró anteriormente Sentry Session Replay y cómo se divide en chunks el trabajo de carga de la página. Se considera terminado cuando Session Replay se carga después de la carga de la página sin afectar a la experiencia del usuario y captura la página solicitada y el uso de las opciones.