fix: add optimistic progress to indexing status report (#887)

This avoids an edge case where users receive a block number from an
indexer but then fail to make a subsequent query to the same indexer
because we think it hasn't hit that block yet.

graph-gateway/src/client_query.rs

@@ -625,7 +625,7 @@ fn build_candidates_list(
             // Infer the indexed range from the indexing progress information
             let range = {
                 let (start, end) = indexing.progress.as_range();
-                start.unwrap_or(0)..=max(end, perf.latest_block + blocks_per_minute)
+                start.unwrap_or(0)..=(max(end, perf.latest_block) + blocks_per_minute)
             };
 
             let number_gte = block_requirements.number_gte.unwrap_or(0);
@@ -644,7 +644,7 @@ fn build_candidates_list(
                     indexing_id.indexer,
                     IndexerError::Unavailable(UnavailableReason::MissingBlock(MissingBlockError {
                         missing: Some(missing),
-                        latest: None,
+                        latest: Some(max(indexing.progress.latest_block, perf.latest_block)),
                     })),
                 );
                 continue;