* use default config for OCDAV_ALLOW_PROPFIND_DEPTH_INFINITY
* remove unnecessary steps
* use default propfind depth infinity value
* use correct step to check the resources
* use correct step to check the resources
* cover depth:infinity enabled test cases
* fix steps
* fix scenario steps
* update expected failure list
* add depth infinity test suite to ci
* update existing tests only
* remove test with depth:infinity
* refactor given and when steps in ocs and webdav locking context
* use the returned response
* use of returned response from helper function
* made changes to the affected test steps
* deleted vardump line
* refactor given when then steps in settings and tus contexts
* set resource location from response
* addressed the reviews
* reset spaceidfromocis
* reset after scenario using after hook
* making helper function, checking and setting response in given step and when steo respectively
* returning response and using in given/then steps as required in favoritesContext
* set the returned response on SpaceContext
* changed to inline variable in some lines as required
* to check for the specific https response code
* migrating set response from helper function to when step in preview feature
* separate single when/then steps by converting to helper function
* use of httpstatuscode check function in given step and rebased
* change function name
* remove use of setresponse in then step
* set the returned response
* enhancement: use kql as default search query language
* enhancement: add support for unicode search queries
* fix: escape bleve field query whitespace
* fix: search related acceptance tests
* enhancement: remove legacy search query language
* enhancement: add support for kql dateTime restriction node types
* chore: bump web to v8.0.0-alpha.2
* fix: failing search api test
* enhancement: search bleve query compiler use DateRangeQuery as DateTimeNode counterpart
* enhancement: support for colon operators in dateTime kql queries
* removing setting response in the given steps
* use response interface
* use the returned response
* check success response
* changed to inline variable
* changed variable response_xml to responseXml
* refactored the user creation given statement from provisioning to graph api
added getUser steps that covers the steps for user with user light role
* added userlight step tests to check drive information and updated expected failure files
* added usercreation initiation code
* deleted seperate tests for user light role
* remove unnecesary changes
* add user not initialize step
* corrected the testcode
* moved the steps from graph to provisioning file
* fix creating single ldap user
* fix: user check method
* initialize user via graph
* addressing reviews
---------
Co-authored-by: Saw-jan <saw.jan.grg3e@gmail.com>
Sagar Gurung