* chore: changed lib
* chore: changed lib
* chore: changed lib
* chore: changed lib
* chore: changes in params
* chore: changes in params
* chore: moving telemetry to a separate package
* feat: enabling telemetry via env var
* chore: removing posthog api_key
* feat: send heartbeat every 6hr
* feat: enabled version in application
* feat: added getter and setter apis and struct for user preferences
* feat: added version to properties to event
* feat: added apis to set and get user preferences and get version
* chore: refactored get and set userPreferences apis to dao pattern
* chore: added checks for telemetry enabled and anonymous during initialization
* chore: changed anonymous user functionality
* chore: sanitization
* chore: added uuid for userPreferences to send when user is anonymous
The flow contains of multiple steps:
* build 'query-service' and 'frontend' images and push them to the image registry
* deploy a disposable k3s cluster
* deploy the app on the cluster
* set a tunnel to allow accessing the UI from the web browser
Signed-off-by: Yoni Bettan <ybettan@redhat.com>