enhancement(compactor): record potential oom risks in compactor components

[Li0k]

1. We adjust the tcp_recv_buffer for the s3 backend implementation. However, this will break when we switch to the opendal_s3 backend.
2. The memory usage estimation algorithm does not take into account different backend implementations.
3. The memory usage estimation algorithm is unable to estimate the memory usage of in-flight uploading sst. (

   risingwave/src/storage/src/hummock/sstable/multi_builder.rs

   Line 305 in 1e84852

   self.sst_outputs.push(SplitTableOutput {

   )

[Li0k]

related to #16685

[hzxa21]

#1682 introduced compactor_concurrent_uploading_sst_count to control the upload concurrency, which can reduce the memory footprint when the object store backend is slow. We decide to rely on this configuration to avoid OOM on non-standard s3 backend to ensure that we will not introduce performance overhead for compaction on s3 backend.