[Sharing-Ng]Add API test coverage for PROPFIND shared resources with same name

[PrajwolAmatya]

Description

Currently, we do not have test coverage for PROPFIND the shared resources with same name. When two users share resource with same name, it is expected to have suffix(1) added on the second share.

Current behavior for PROPFIND request of the shared resources for old and new dav path returns suffix(1) in the response as <oc:name>test-folder (1)</oc:name>. In case of spaces dav path the response returns <oc:name>test-folder</oc:name>.

Cover tests for old , new and spaces dav paths

• Add test coverage for PROPFIND of shared resources with same name.
  • [full-ci] [tests-only] Added tests for PROPFIND as sharee #8622
  • [full-ci] [tests-only] Added tests for PROPFIND as sharee for folder #8671
  • [full-ci] [tests-only] sharee PROPFINDs same name shares shared by multiple users #8674
  • [full-ci] [tests-only] sharee PROPFINDs on resource containing brackets #8675
• Match the ids between share and propfind responses (DriveItem ID from listSharedWithMe doesn't match with shared resource id #8420) @PrajwolAmatya [tests-only][full-ci] added test to check id from shareWithMe and PROPFIND response #8767

- [ ] shareid (#8510)

Related issues:

• PROPFIND to sub-folder of a shared resources with same name gives 404[old/new dav path] #3859
• PROPFIND on accepted shares with identical names containing brackets exit with 404 [spaces dav path] #4421
• DriveItem ID from listSharedWithMe doesn't match with shared resource id #8420
• Missing shareid on response of a PROPFIND on the sharejail root #8510

[grgprarup]

Tests coverage for Add test coverage for PROPFIND of shared resources with same name are added and all related PRs are merged.

[PrajwolAmatya]

• Match the ids between share and propfind responses (DriveItem ID from listSharedWithMe doesn't match with shared resource id #8420) @PrajwolAmatya

Which ids are we actually checking here? Checking fileid has been already covered in #8674 and we do not get shareid in the PROPFIND response.
cc @amrita-shrestha @nabim777 @saw-jan

[nirajacharya2]

From the list of issues mentioned above in the description, only one issue #8510 is remained as bug. So, it will be tracked in #8428
So closing this issue.