HDDS-7713. listKeys with prefix path as key for FSO buckets is redundant

[Tejaskriya]

What changes were proposed in this pull request?

The redundant listing of keys was originating from the client module (it was visible from both aws s3 ls and ozone sh key list interfaces). The change proposed is to not add the prefix to the result list if the prefix is for a key and not a directory.

What is the link to the Apache JIRA

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

How was this patch tested?

Tested manually using docker.
Through S3:

$ aws s3 ls --endpoint http://localhost:9878 s3://buck1/k1  
2023-08-10 13:37:14          3 k1

Through ozone sh:

$ ozone sh key list s3v/buck1 --prefix k1
[ {
  "volumeName" : "s3v",
  "bucketName" : "buck1",
  "name" : "k1",
  "dataSize" : 3,
  "creationTime" : "2023-08-10T08:07:13.130Z",
  "modificationTime" : "2023-08-10T08:07:14.138Z",
  "replicationConfig" : {
    "replicationFactor" : "THREE",
    "requiredNodes" : 3,
    "replicationType" : "RATIS"
  },
  "metadata" : { },
  "file" : true
} ]

Also added a test in testListKeysAtDifferentLevels() of TestObjectStoreWithFSO.

[whbing]

LGTM Overall. Thanks ! Here's a minor suggestion from my perspective.
We can add test in TestListKeysWithFSO to compare the listKeys results of legacyBucket and fsoBucket. I've written a demo test in TestListKeysWithFSO:

  @Test
  public void testListKeysWithValidStartKey() throws Exception {
    // case-10: keyPrefix corresponds an exist file
    expectedKeys =
        getExpectedKeyList("a1/b3/e3/e31.tx", "", legacyOzoneBucket);
    checkKeyList("a1/b3/e3/e31.tx", "", expectedKeys, fsoOzoneBucket);
  }

Result will be Actual :[a1/b3/e3/e31.tx, a1/b3/e3/e31.tx] without PR （Test Failed） and Actual :[a1/b3/e3/e31.tx] with this PR （Test passed）.

[whbing]

NIT: title can be specified FSO

[Tejaskriya]

// case-10: keyPrefix corresponds an exist file
    expectedKeys =
        getExpectedKeyList("a1/b3/e3/e31.tx", "", legacyOzoneBucket);
    checkKeyList("a1/b3/e3/e31.tx", "", expectedKeys, fsoOzoneBucket);

Thank you for the suggestion, I have added the test case you've specified in TestListKeysWithFSO

[whbing]

+1, once ci passed.

[sadanand48]

LGTM

[aryangupta1998]

LGTM, +1

[sadanand48]

Thanks @Tejaskriya for the patch, @whbing @aryangupta1998 for the review.