feat: Add write_total_max_size in Capability

[poltao]

For #3216 , D1 limited the Maximum string, BLOB or table row size to 1M, but gen_bytes() randomly generates 1~4M content. It will result in the following error:

D1Response { result: [], success: false, errors: [D1Error { message: "string or blob too big", code: 7500 }], messages: [] }

Maybe we can support configuring max_size via environment variable?

[Xuanwo]

I prefer addressing this issue from service capability side.

[poltao]

I prefer addressing this issue from service capability side.

I'm not sure I understand what you mean. How do we addressing this issue from service capability side?
And when the randomly generated content is greater than 1m, behavioral tests can fail, don't we need to be concerned?

[Xuanwo]

I'm not sure I understand what you mean. How do we addressing this issue from service capability side?

I haven't thought about this deeply yet, but perhaps we can consider adding a write_total_max_size to the Capability like this:

https://github.com/apache/incubator-opendal/blob/82f98772363a1548f9184c07f58cc85fcdf857ae/core/src/types/capability.rs#L89-L92

This way, both users and our tests can determine the maximum size supported by this service.

[poltao]

@Xuanwo Add new capability attribute write_total_max_size, plz help review.

[Xuanwo]

Great!

[Xuanwo]

The only task here is to make clippy happy:

error: using `clone` on type `Capability` which implements the `Copy` trait
   --> core/tests/behavior/blocking_write.rs:435:34
    |
435 |     let (content, _) = gen_bytes(op.info().full_capability().clone());
    |                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try removing the `clone` call: `op.info().full_capability()`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#clone_on_copy