Add reindex capability to remote store protocol (#8985)

### Related

Part of rerun-io/dataplatform#156.

### What

We want to be able to manually request the reindexing of an existing
index. This could be used after a recording is added, which leaves the
index in a stale state.

.gitignore

@@ -75,3 +75,6 @@ justfile
 
 # heaptrack files
 *.zst
+
+# IDE stuff
+/.idea

crates/store/re_protos/proto/rerun/v0/remote_store.proto

@@ -10,6 +10,7 @@ service StorageNode {
     rpc FetchRecording(FetchRecordingRequest) returns (stream rerun.common.v0.RerunChunk) {}
 
     rpc CreateIndex(CreateIndexRequest) returns (CreateIndexResponse) {}
+    rpc ReIndex(ReIndexRequest) returns (ReIndexResponse) {}
 
     // The response to `SearchIndex` a RecordBatch with 3 columns:
     // - 'resource_id' column with the id of the resource
@@ -74,6 +75,13 @@ message CreateIndexRequest {
     rerun.common.v0.IndexColumnSelector time_index = 4;
 }
 
+message ReIndexRequest {
+    // which catalog entry do we want to reindex for
+    CatalogEntry entry = 1;
+    // which column do we want to reindex
+    IndexColumn column = 2;
+}
+
 message IndexProperties {
     oneof props {
         InvertedIndex inverted = 1;
@@ -109,6 +117,9 @@ message CreateIndexResponse {
     uint64 indexed_rows = 1;
 }
 
+message ReIndexResponse {
+}
+
 // ---------------- SearchIndex ------------------
 
 message SearchIndexRequest {