HDDS-11774. Adding listing metadata flag to resolve client incompatibility for listing

[swamirishi]

What changes were proposed in this pull request?

Creating a generic metadata map in the OMRequest to deal with client version incompatibility. Setting a key in the client request to the map for server to act on the basis of the value set by the client.

What is the link to the Apache JIRA

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

How was this patch tested?

Planning to add a compatibility test for this.

[fapifta]

QQ, why aren't we bump the client version instead to (client supports server side liststatus limits or something like that), so that we can identify older clients that does not know about/respect the server side limit, and then we can treat these clients from the server side?

At least my understanding is that about the current draft that it pushes this client information via a request metadata instead of with the client's version, but please correct me if I am wrong.

[swamirishi]

QQ, why aren't we bump the client version instead to (client supports server side liststatus limits or something like that), so that we can identify older clients that does not know about/respect the server side limit, and then we can treat these clients from the server side?

At least my understanding is that about the current draft that it pushes this client information via a request metadata instead of with the client's version, but please correct me if I am wrong.

You are right @fapifta we can achieve this by a client version bump and that is eventual goal. But because our request feature validator is broken we cannot bump up our client version. We already have a patch upstream which fixes that #6932 . I thought to have a patch in the interim. But after discussing about this offline with @errose28 @prashantpogde @umamaheswararao @swagle we came to a conclusion to abandon this change and work on merging the request feature validator fix and perform a client version bump up instead.