Add ID filtering to AuctionsRequest; add local_seq to AuctionsResponse

proto/penumbra/penumbra/view/v1/view.proto

@@ -147,13 +147,17 @@ service ViewService {
   rpc Auctions(AuctionsRequest) returns (stream AuctionsResponse);
 }
 
+// Filters in an `AuctionsRequest` will be combined using `AND` logic -- that
+// is, the more filters you add, the fewer responses you're likely to get.
 message AuctionsRequest {
   // If present, filter balances to only include the account specified by the `AddressIndex`.
   core.keys.v1.AddressIndex account_filter = 1;
   // If present, include inactive auctions as well as active ones.
   bool include_inactive = 2;
   // If set, query a fullnode for the current state of the auctions.
   bool query_latest_state = 3;
+  // If present, filter to only include auctions whose IDs are in this array.
+  repeated core.component.auction.v1.AuctionId auction_ids_filter = 4;
 }
 
 message AuctionsResponse {
@@ -170,6 +174,16 @@ message AuctionsResponse {
   // Only present when `query_latest_state` was provided.
   // Could be empty, depending on the auction state.
   repeated core.component.dex.v1.Position positions = 3;
+  // The sequence number of the auction state _as known to the local view
+  // service_. Note that the local view service may lag behind the fullnode. For
+  // example, if the chain hits an auction's `end_height`, but the user hasn't
+  // yet exchanged their sequence-0 (opened) auction NFT for a sequence-1
+  // (closed) auction NFT, the local view service will have a sequnce number of
+  // 0.
+  //
+  // Dutch auctions move from:
+  // 0 (opened) => 1 (closed) => n (withdrawn)
+  uint64 local_seq = 5;
 }
 
 message AuthorizeAndBuildRequest {