Mandatorily wrap _read_chunk in a check_chunk_n decorator

[dachengx]

What is the problem / what does the code in this PR do

To ease the workflow of developing a new StorageBackend, the PR mandatorily wraps _read_chunk in a check_chunk_n decorator instead.

Can you briefly describe how it works?

Can you give a minimal working example (or illustrate with a figure)?

Please include the following if applicable:

• Update the docstring(s)
• Update the documentation
• Tests to check the (new) code is working as desired.
• Does it solve one of the open issues on github?

Please make sure that all automated tests have passed before asking for a review (you can save the PR as a draft otherwise).

[github-actions]

coverage: 91.439% (-0.02%) from 91.454% when pulling 4cbc457 on chunk_n_backend into 1ca53c6 on master.

[JYangQi00]

Thanks Dacheng,

I just want to make sure I'm understanding this correctly, so please correct me if I am wrong. The point of this PR is just to reduce code duplication by making the wrapper apply to every instance of a StorageBackend via the __new__ class, correct? If so, this PR looks good to me and I will accept

[dachengx]

Thanks Dacheng,

I just want to make sure I'm understanding this correctly, so please correct me if I am wrong. The point of this PR is just to reduce code duplication by making the wrapper apply to every instance of a StorageBackend via the __new__ class, correct? If so, this PR looks good to me and I will accept

Thanks. Yes, you are correct.