gdk pristine should clear Zoekt related data
Overview
gdk pristine should also clear out zoekt data
Impacted categories
The following categories relate to this issue:
- 
gdk-reliability - e.g. When a GDK action fails to complete. 
- 
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. 
- 
gdk-performance - e.g. When a GDK action is slow or times out. 
Steps to replicate (optional)
Proposal (optional)
gdk pristine must delete files in zoekt-data/development/index and zoekt-data-development/index-2. That could be done using the truncate api call to zoekt or OS calls
It may reindex zoekt data, but that might be too much work for an initial implementation. Users can manually reindex using other methods.
Environment (optional)
- Operating system name: <!-- output of `uname -a` command -->
- Architecture: <!-- output of `arch` command -->
- The contents of your gdk.yml(if any)
- Ruby version: <!-- output of `ruby --version` command -->
- GDK version: <!-- output of `git rev-parse --short HEAD` command -->