cluster_link/model: change default max partition bytes

Prior to this commit the default max partition bytes was 1MiB. The
default min fetch bytes was 5MiB. And the max wait ms was 500ms.

In cases where only one partition on the shard was being produced to
these defaults limited our consumer throughput to 2MiB/s. This is since
we'd only be able to read 1MiB every 500ms from the one partition with
new data.

Hence this commit sets max partition bytes to equal min fetch bytes to
prevent this issue.

Author: ballard26

proto/redpanda/core/admin/v2/shadow_link.proto

@@ -290,7 +290,7 @@ message ShadowLinkClientOptions {
     int32 effective_fetch_max_bytes = 17
         [(google.api.field_behavior) = OUTPUT_ONLY];
     // Fetch partition max bytes.
-    // If 0 is provided, defaults to 1 MiB
+    // If 0 is provided, defaults to 5 MiB
     int32 fetch_partition_max_bytes = 18;
     // The effective fetch partition max bytes
     int32 effective_fetch_partition_max_bytes = 19

src/v/cluster_link/model/types.h

@@ -276,7 +276,7 @@ struct connection_config
     // fetch response.
     std::optional<int32_t> fetch_partition_max_bytes;
     // Default maximum number of bytes to fetch per partition
-    static constexpr auto default_fetch_partition_max_bytes = 1_MiB;
+    static constexpr auto default_fetch_partition_max_bytes = 5_MiB;
     // Default maximum number of bytes to fetch (20MiB)
     static constexpr auto fetch_max_bytes_default = 20 * 1024 * 1024;
 

tests/rptest/clients/admin/proto/redpanda/core/admin/v2/cluster_pb2.pyi

@@ -270,9 +270,9 @@ def test_create_default_link(self):
             f"Expected 0, got {client_options.fetch_partition_max_bytes}"
         )
         assert client_options.effective_fetch_partition_max_bytes == (
-            1 * 1024 * 1024
+            5 * 1024 * 1024
         ), (
-            f"Expected {1 * 1024 * 1024}, got {client_options.effective_fetch_partition_max_bytes}"
+            f"Expected {5 * 1024 * 1024}, got {client_options.effective_fetch_partition_max_bytes}"
         )
 
         topic_metadata_config = shadow_link.configurations.topic_metadata_sync_options