Consider removing unencrypted rsync server

I have established a new server to replace the final remaining server running on equinix, the 'unencrypted' server. (https://github.com/nodejs/build/issues/3597)

This server is in the OpenJS Azure account where we have a substantial usage credit.

This server is still offering an rsync endpoint, which it rsync's from the www server daily.

The current rsync services have been advertised as "going away" on 2022-01-01, but that clearly hasn't happened yet.

ryan@DESKTOP-P5AM10H:~$ rsync rsync://unencrypted.nodejs.org
nodejs          Node.js releases. This service expires 2022-01-01.
iojs            io.js releases. This service expires 2022-01-01.

Additionally, unencrypted.nodejs.org is listed as a member of two Cloudflare load balancer pools, one of which (nodejs.org) is disabled, and the other "origin.nodejs.org" is still enabled.

I'm ready to switch the DNS for unencrypted so the rsync service continues until we can figure out whether its actually needed anymore and whether or not we have a communication plan to disable that service (if we can).

I'm wondering if the load balancer is even necessary at this point, as I'm pretty sure that's not even being used anymore with the R2/worker based delivery of dist.

Im not going to deploy on a friday before a Holiday weekend, but would like to do this ASAP next week.

Start by verifying the unencrypted.nodejs.org rsync endpoint, its DNS, and its membership in the two Cloudflare load-balancer pools described in the issue. Check whether the service is still needed and whether the R2/worker delivery path uses it; the work is done when its dependencies and communication plan are resolved and the server can be safely retired or its DNS role changed.