Explicit set utf-8 headers for file operations

[tschechniker]

File operations need to have utf-8 headers otherwise special allowed characters will break the file action as they will encoded to ascii per default.

Fixes #

If you have files with äöü etc. you will get an ascii encoding error cause of the reference in the Header.

This fixes this issue

Changes proposed in this pull request:

• Set Headers to encode to UTF-8 on file operations

[bigcat88]

@tschechniker

Thanks for the pull request, and I have a question.
Can you describe a situation when the current code does not work correctly?
Which language needs to be set with which symbols in path to see the error?

I wanted to add a test for this

[tschechniker]

@bigcat88

it's easy.

Scenario to reproduce:

Create a file /documents/MyTestDocumentä.doc

then try to move it with files.move to e.g. /trash/MyTestDocumentä.doc

Important here is that the destination contains the "ä" because the destination is the value added to the header field.

/document/MyTestDocumentä.doc -(move)-> /trash/MyTestDocument.doc WORKS
/document/MyTestDocument.doc -(move)-> /trash/MyTestDocumentä.doc NOT WORKING
/document/MyTestDocumentä.doc -(move)-> /trash/MyTestDocumentä.doc NOT WORKING

This also happens with all non ASCII chars which are allowed as file or folder names in nextcloud. For example äöü from german umlauts.

[codecov]

Codecov Report

Merging #157 (891da4c) into main (0372e78) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   99.77%   99.77%           
=======================================
  Files          34       34           
  Lines        3134     3134           
=======================================
  Hits         3127     3127           
  Misses          7        7           

Files	Coverage Δ
nc_py_api/files/files.py	99.25% <100.00%> (ø)

[bigcat88]

I will add tests for this later today(and probably will check __upload_stream as it uses the Destination header, too).
Thank you again.