[backport] rafs: avoid a debug_assert related to v5 amplify io

[bergwolf]

backport master commit

commit 251730990ebc4a008b231d46c2315e1fc372f889
Author: Jiang Liu <gerry@linux.alibaba.com>
Date:   Sun Apr 30 17:10:00 2023 +0800

    rafs: avoid a debug_assert related to v5 amplify io

    In function RafsSuper::amplify_io(), is the next inode `ni` is
    zero-sized, the debug assertion in function calculate_bio_chunk_index()
    (rafs/src/metadata/layout/v5.rs) will get triggered. So zero-sized
    file should be skipped by amplify_io().

    Signed-off-by: Jiang Liu <gerry@linux.alibaba.com>

Relevant Issue (if applicable)

If there are Issues related to this PullRequest, please list it.

Details

Please describe the details of PullRequest.

Types of changes

What types of changes does your PullRequest introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

Go over all the following points, and put an x in all the boxes that apply.

• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[anolis-bot]

@bergwolf , a new test job has been submitted. Please wait in patience. The test job url: https://tone.openanolis.cn/ws/nrh4nnio/test_result/84399

[anolis-bot]

@bergwolf , The CI test is completed, please check result:

Test Case		Test Result
build rust golang image		✅ SUCCESS
compile nydusd		✅ SUCCESS
compile ctr remote		✅ SUCCESS
compile nydus snapshotter		✅ SUCCESS
run container with rafs		✅ SUCCESS
run container with zran		✅ SUCCESS
run container with rafs and compile linux		✅ SUCCESS

Congratulations, your test job passed!