HTTPS: Fix PUT resume

[mihaigalos]

PUT resume was tested with 2 files: 1st file was put and then the 2nd one.
Since they had the same name, the upload was resumed.
This, however, does not guarantee that a full resume is possible, since getting the problem lies in the getting of the already uploaded bytes.

EDIT: Consider using POST to rewrite the file entirely (no resume possible).

Fixes: #57.

[codecov-commenter]

Codecov Report

Merging #56 (5f81857) into main (d19e192) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   96.93%   96.93%           
=======================================
  Files          17       17           
  Lines        1075     1076    +1     
=======================================
+ Hits         1042     1043    +1     
  Misses         33       33           

Impacted Files	Coverage Δ
src/ftp.rs	97.01% <100.00%> (ø)
src/https.rs	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d19e192...5f81857. Read the comment docs.

[mihaigalos]

Will stop pursuing this, since a server-side WebDAV config supporting PUT ranges is necessary.
I don't yet know how to enable this in the CI/local testing using the nginx.conf.