Telemetry to guide investment decisions

As maintainers, we do not currently have a way to gauge feature popularity in the community. This makes it more difficult to identify the most impactful work areas and conversely what we should deprecate. The crawler that previously existed to help with this was removed because it was unmaintained: https://github.com/kubernetes-sigs/kustomize/pull/3841. Let's resurrect this in some form.

We could also consider an opt-in mechanism to report feature usage at build time. This has serious privacy implications to consider.

Start by reviewing pull request #3841, which removed the previous crawler, and the privacy concern described in this issue. Clarify the telemetry scope, opt-in requirements, and acceptance criteria with maintainers; the issue is not complete until an agreed approach and its privacy boundaries are defined.

Written by the indexing model from the issue text.