feat: add new.stats jenkins.io CNAME record

[lemeurherve]

This PR adds new.stats CNAME record that will be used for serving the new stats website content.

Note: using "new.stats" subdomain until the corresponding GSoC project is ready to replace the existing stats.jenkins.io

Ref:

• To host stats.jenkins.io GSoC 2024 project in jenkins-infra helpdesk#4132 (comment)

[dduportal]

Blocking until we have a plan defined, discussed and agreed on for jenkins-infra/helpdesk#4132 (comment) (e.g. do we need Fastly and why?)

[lemeurherve]

I've followed the same model as the other websites.

Answered at jenkins-infra/helpdesk#4132 (comment),

Using it as CDN, same logic as for other websites like jenkins.io, stories.jenkins.io, contributors.jenkins.io, docs.jenkins.io.

The website would be served from a nginx on publick8s at (new.)stats.origin.jenkins.io like the others.

[lemeurherve]

Quoting my reply from jenkins-infra/helpdesk#4132 (comment):

As stats.jenkins.io is currently hosted on GitHub Pages, I'm not sure we can access traffic stats from it. I found https://github.blog/2014-01-07-introducing-github-traffic-analytics/ but it doesn't seem active anymore.

Then I don't think there's a lot of traffic on these pages, we can start serving it without Fastly then see what are the actual numbers in term of visits.

Removing the Fastly step points and reworking jenkins-infra/azure-net#257

PR reworked accordingly.

[dduportal]

Plan: 1 to add, 0 to change, 0 to destroy.