fix: flowctl catalog does need pagination after all

Was having a weird issue where `flowctl catalog pull-specs --captures=true --collections=true` wasn't returning any captures, but `flowctl catalog pull-specs --captures=true --collections=false` was, and realized that the first command was returning exactly 1000 specs. Turns out that even though we're paginating the inputs, we still need to paginate the queries themselves.

crates/flowctl/src/catalog/mod.rs

@@ -6,9 +6,13 @@ mod test;
 use crate::{
  api_exec, api_exec_paginated, controlplane,
  output::{to_table_row, CliOutput, JsonCell},
+ pagination::into_items,
 };
 use anyhow::Context;
-use futures::stream::{FuturesUnordered, StreamExt};
+use futures::{
+ stream::{FuturesUnordered, StreamExt},
+ TryStreamExt,
+};
 use itertools::Itertools;
 use models::{CatalogType, RawValue};
 use serde::{Deserialize, Serialize};
@@ -260,7 +264,7 @@ where
  let builder = builder.clone().in_("catalog_name", batch);
  async move {
  // No need for pagination because we're paginating the inputs.
- api_exec::<Vec<T>>(builder).await
+ into_items::<T>(builder).try_collect::<Vec<T>>().await
  }
  })
  .collect::<FuturesUnordered<_>>();