feat: Add start-after support for list

[Xuanwo]

Some services support list from start-after, like s3, gcs. We can provide this feature to allow users to resume their list process.

Tasks

• core: Add start-after for OpList and add into capability #2069 @lexcao
• Add start-after support for s3
• Add start-after support for gcs

[lexcao]

Hi @Xuanwo , I am willing to help on this.

[Xuanwo]

Great! Have fun! I will assign you to the first task.

[lexcao]

Hi @Xuanwo, I am willing to help the rest of 2 tasks.

[Xuanwo]

Hi @Xuanwo, I am willing to help the rest of 2 tasks.

Great! Maybe we can add a behavior test case for start after first🤩

[lexcao]

Thank you!
Sure, I will give it a try.

[Xuanwo]

I have assigned this issue to you, take your time and have fun!

[lexcao]

Hi, @Xuanwo , need help with the details about behavior test before coding.

Here is what the structure of the behavior test for test_list_with_start_after could be:

// in file tests/behavior/list.rs
pub async fn test_list_with_start_after(op: Operator) -> Result<()> {
    // 1. check the capability
    // 2. write test data
    // 3. list with start-after
    // 4. assert the result
    // 5. clear data
}

• Could you please help reviewing the structure? I want to confirm I am in the right way to add a behavior test.

• How do I test it without implementing the real backend(e.g s3 and gcs)?

[Xuanwo]

• Could you please help reviewing the structure? I want to confirm I am in the right way to add a behavior test.

LGTM!

• How do I test it without implementing the real backend(e.g s3 and gcs)?

It's Ok to implement for s3 first.

[lexcao]

Great, your quick response is appreciated.
I am going to code. 🚀

[lexcao]

All sub-tasks finished, this issue could be closed as well.

[Xuanwo]

Thanks a lot!