refactor!: Remove stat_has_xxx and list_has_xxx

[Xuanwo]

Which issue does this PR close?

As suggested in #5557 (comment)

Rationale for this change

Make code more readable and maintainable.

What changes are included in this PR?

Remove all stat_has_xxx and list_has_xxx fields.

Are there any user-facing changes?

Capability removed.

[killme2008]

@Xuanwo @yihong0618 GreptimeDB used list_has_content_length to determine whether to call stat again:

https://github.com/GreptimeTeam/greptimedb/blob/d774996e89648dbdf25326cc8440b51847095abb/src/object-store/src/layers/lru_cache/read_cache.rs#L163

Since it’s been removed, is there a replacement API?

Looks like it's always true, so maybe I can just remove this checking.

Thank you.

[Xuanwo]

Since it’s been removed, is there a replacement API?

Looks like it's always true, so maybe I can just remove this checking.

Sorry this change broke your use case. Could you please open a new issue? I believe we can come up with a new design to address it.

[killme2008]

Since it’s been removed, is there a replacement API?
Looks like it's always true, so maybe I can just remove this checking.

Sorry this change broke your use case. Could you please open a new issue? I believe we can come up with a new design to address it.

Sure!