cephfs: add clone progress report in clone status

[Nikhil-Ladha]

Add clone progress report in clone status output

Checklist

• Added tests for features and functional changes
• Public functions and types are documented
• Standard formatting is applied to Go code
• Is this a new API? Added a new file that begins with //go:build ceph_preview
• Ran make api-update to record new APIs

New or infrequent contributors may want to review the go-ceph Developer's Guide including the section on how we track API Status and the API Stability Plan.

The go-ceph project uses mergify. View the mergify command guide for information on how to interact with mergify. Add a comment with @Mergifyio rebase to rebase your PR when github indicates that the PR is out of date with the base branch.

[Nikhil-Ladha]

Ref issue: ceph/ceph-csi#4813

[phlogistonjohn]

I see that this is an admin API, so it should be populating the new struct via JSON. However, I would like to see tests for this prior to approval.

[Nikhil-Ladha]

I see that this is an admin API, so it should be populating the new struct via JSON. However, I would like to see tests for this prior to approval.

Tests as in that the json/struct is populated correctly or something else?

[phlogistonjohn]

Tests as in that the json/struct is populated correctly

That would be fine thanks.

[Nikhil-Ladha]

I have added a json sample for test TestParseCloneStatus under clone_test.go file, hope that helps.
I have tested locally the TestCloneSubVolumeSnapshot with fmt.Printf() statements under parseCloneStatus function and the value was propagated properly.

[nixpanic]

please correct the formatting/indention