HDDS-14659. Add new proto message for lightweight MultipartPartInfo

[devabhishekpal]

What changes were proposed in this pull request?

HDDS-14659. Add new proto message for lightweight MutlipartPartInfo

Please describe your PR in detail:

• Currently the PartKeyInfo message is a huge object including several repeated fields from KeyInfo. This is not required as the parent MultipartKeyInfo message already includes some common fields
• As part of this patch we are introducing a new proto message MultipartPartInfo. This contains the absolutely essential fields required for any given part and drops any extra fields.
• We also update MultipartKeyInfo message to pull in common metadata fields like volumeName, bucketName, keyName.
• We also add a field schemaVersion which will help us with deciding whether to use a new flow for writing MPU parts, or use the currently approach of storing parts inline.

Reference design doc: #9793

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-14659

How was this patch tested?

Patch was tested via unit tests, but currently this change will not affect any behaviour.

[adoroszlai]

Thanks @devabhishekpal for the patch.

[adoroszlai]

Thanks @devabhishekpal for updating the patch, LGTM. Let's wait for others to take a look.

[devabhishekpal]

@ChenSammi @ivandika3 @errose28 could you take a look at this patch?

[ChenSammi]

LGTM +1.

[rakeshadr]

Can you check whether "optional string ownerName" is required at part level. For example, any auditing purpose. Earlier, this was stored indirectly through KeyInfo.

[devabhishekpal]

I think per part owner metadata is not required.
This was mostly incidental metadata as enforcement of ACL did not rely on per-part owner. Also I think checks on native authorizer is done on bucket level for listing operations. But maybe key write does open key ACL check for that write.

I think owner metadata and acls can be pulled up to the MultipartInfo message as that is the equivalent of a key. Let me do that.