ArtifactoryPath.set_properties should use Update item properties API instead

[gangefors]

There is an issue with using the Set item properties API in artifactory. When setting a lot of properties you can run into the issue where the URI becomes too long.

If set_properties use the Update item properties API no such issue exists since it takes json data as input with a PATCH request.

https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-UpdateItemProperties

The request can add, update and delete properties which means that it can basically do all actions one wants to do with properties.

Should a new method be implemented (update_properties) or should set_properties be rewritten to use the update item properties API? Because I'm willing to do a PR for this as long as I know how you want it implemented.
Using a new method will mirror the API endpoins that exist. But updating set_properties will remove the issue with URI too long.

[kvecchione]

This update is causing an issue for us, recursive=0 is set on the PATCH but properties are still being set recursively when that is not desired.

[beliaev-maksim]

@kvecchione
please open a new issue and provide a minimum reproducible snippet

[kvecchione]

#326