Telemetry improvements

What

• Since the CMake-based module census is limited to projects changing, Qt Creator shall gather information about used modules also while building. 
• The current regrettable hack of bundling all data into the key of the interaction shall be converted to proper use after the Qt Insight supports storing structured data. 
• Extend gathered telemetry with information about created projects (template, language, ...), opened examples and other home-mode content. 
• Qt Creator's Sentry shall not contain information about other processes than Qt Creator itself. 

Why

• The current gathering method does not provide information on projects whose configuration remains stable (e.g. during February 2025 Qt Insight collected ~500K entries from Qt Creator, of which ~200 contained module listing information, 0.04% hit rate). 
• The current storing method is as architecturally unsound as they come. 
• Qt lacks data on how provided content is used and on what kinds of projects users are developing. 
• Qt does not need to collect any data about any other processes than Qt Creator itself.

Dependencies

• Qt Insight

User stories / Acceptance criteria

• Qt shall be aware of what modules are used.
• Qt shall be aware of what kinds of projects are created.
• Qt shall be aware of what kinds of content users consume. 
• Qt Creator shall not store data to Sentry about any other processes than Qt Creator. 

Tasks

• investigate extending the current data collection mechanism with a parallel schema: injecting the data gathering to another user interaction - possibly project building
• investigate additional telemetry data requirements (e.g. use of examples, tutorials, learning materials)
  • https://intranet.qt.io/pages/viewpage.action?pageId=248840714
• additional tasks based on the above
• clarify the schedule of the proper structured data storage in Qt Insight
  • https://bugreports.qt.io/browse/ANALYTICS-1186