[FEAT] Telemetry

[gmartinsribeiro]

Is your feature request related to a problem? Please describe.
Similarly to the issue opened for ydata-profiling, the goal is to better understanding how ydata-synthetic is being used to prioritize and drive product innovation.
There are many questions we can answer now that could help a lot making the product better:

• Which versions of ydata-synthetic are people installing/using now (i.e. whether people have primarily made the jump from version X to version Y)
• Which Python version / environment is used, among other env specs?
• What features are the most used and wanted?
• Approximately how many people out there in the world are installing ydata-synthetic?
• Is ydata-synthetic being used for ad-hoc developments or part of CI/CD pipelines?
• and many more.

Describe the solution you'd like
My proposal is to use Scarf.sh.
The following case studies are worth reading:

1. https://about.scarf.sh/post/scarf-case-study-apache-superset
2. https://about.scarf.sh/post/haskell-org-bridging-the-gap-between-language-innovation-and-community-understanding

Similar to them, this could help in various ways that come with using data for decision-making. With clear guidelines on "how to opt-out" & "what data is being collected", this can be beneficial to the entire community as we would be making more informed decisions.

Describe alternatives you've considered
It's possible to find other tools for telemetry, but this one seems to check all the boxes.

Additional context
The ASF already approves Scarf and is already used by other ASF projects, namely Superset, Dolphin Scheduler, Dubbo Kubernetes, DevLake, Skywalking as it follows GDPR and other regulations.