doc: remove GA tracking

[bnoordhuis]

The Google Analytics tracking wasn't wholly uncontroversial and hasn't
been used in practice. Remove it.

Refs: #6601
Fixes: #22652

[nodejs-github-bot]

@bnoordhuis build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1010/pipeline

[trivikr]

RSLGTM

[MylesBorins]

are we sure it is unused? /cc @nodejs/community-committee

[amiller-gh]

Only use I've seen of the data is to help guide some focus in the website rede#itiative, but it didn't do much other than confirm already existing assumptions.

I'm personally always in favor of collecting more data on the off chance we need it / will find it useful in the future – but I also respect and understand the privacy concerns expressed by other people here, so I don't want to block this from happening unless others feel strongly to the contrary.

@bnb, any historical knowledge on how GA tracking has been used?

[silverwind]

Access logs are a better source for such data because I guess among the developer community, a reasonable amount of users would use a tracking blocker and these users would not be picked up by GA, but would still be visible in the access logs.

[keywordnew]

I'm not familiar with the process to getting a hold of those. Are access logs a resource that to which we have reasonable access?

If we have (better) alternatives to the data collected by GA, then it would seem unnecessary.

[danbev]

CI: https://ci.nodejs.org/job/node-test-pull-request/17486/

[silverwind]

Are access logs a resource that to which we have reasonable access?

I'm not that deeply involved in the organization, but I guess one could set up a log parser which can present similar stats than GA, without privacy concerns.

[refack]

Are access logs a resource that to which we have reasonable access?

I'm not that deeply involved in the organization, but I guess one could set up a log parser which can present similar stats than GA, without privacy concerns.

I think ATM this falls under the BuildWG's responsibility. The current setup of the WWW server is mirrored in the scripts at https://github.com/nodejs/build/tree/master/setup/www (server is NGINX).
We already parse the logs to produce download statistics, but if we want stats on */api/*, something will need to be implemeted/developed.

[refack]

P.S. this PR will probably not affect the existing documentation already deployed to the site:

[addaleax]

Thank you.

[addaleax]

Rebuild CI: https://ci.nodejs.org/job/node-test-pull-request/17522/

[danbev]

Re-run of failing node-test-commit-arm ✔️
Re-run of failing node-test-commit-windows-fanned ✔️

[danbev]

Landed in df6a130.