HDDS-14611. Rename committed bytes to finalized key bytes and align committed space terminology

[priyeshkaratha]

What changes were proposed in this pull request?

The term committed used in the code to indicate the pre-allocated commit bytes in the storage report. But in StorageDistribution report committed used is to indicate the total bytes completed/finalized written to ozone. So here refactoring the code to change pre-allocated container bytes use term committed for writen complete size user the tern finalizedKeyBytes.

What is the link to the Apache JIRA

HDDS-14611

How was this patch tested?

Tested using existing unit testcase and integration tests.
Tested UI integration manually

[sreejasahithi]

Thanks @priyeshkaratha for working on this.

I think we should consider updating capacity.constants.tsx to use the new field names or was this intentional?:

ozone/hadoop-ozone/recon/src/main/resources/webapps/recon/ozone-recon-web/src/v2/constants/capacity.constants.tsx

Line 28 in 0c04347

totalOzonePreAllocatedContainerSpace: 0,

totalOzonePreAllocatedContainerSpace: 0 -> totalOzoneCommittedSpace: 0

ozone/hadoop-ozone/recon/src/main/resources/webapps/recon/ozone-recon-web/src/v2/constants/capacity.constants.tsx

Line 41 in 0c04347

committedKeyBytes: 0

committedKeyBytes: 0 -> finalizedKeyBytes: 0

[priyeshkaratha]

I think we should consider updating capacity.constants.tsx to use the new field names or was this intentional?:

I couldn't get your point. Renaming already considered.

[sreejasahithi]

I think we should consider updating capacity.constants.tsx to use the new field names or was this intentional?:

I couldn't get your point. Renaming already considered.

Right, this is already fixed. Sorry for the confusion I missed this change in my review. Thanks for clarifying!