🐛 Fix webserver storage OpenAPI schema

[GitHK]

What do these changes do?

• fixes a regression introduced in ♻️Storage API specs are now autogenerated 🚨 #4413
• 🐛 fixed an issue with the abort file endpoint not having the correct permissions (this is currently broken on all deployments)
• added regression tests

Related issue/s

How to test

DevOps Checklist

[codeclimate]

Code Climate has analyzed commit ebbc7e5 and detected 0 issues on this pull request.

View more on Code Climate.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.1% Duplication

[codecov]

Codecov Report

Merging #4426 (ebbc7e5) into master (03dc50a) will decrease coverage by 1.2%.
The diff coverage is 100.0%.

@@            Coverage Diff            @@
##           master   #4426      +/-   ##
=========================================
- Coverage    85.9%   84.8%    -1.2%     
=========================================
  Files         952     395     -557     
  Lines       41702   20791   -20911     
  Branches     1004     173     -831     
=========================================
- Hits        35849   17641   -18208     
+ Misses       5619    3101    -2518     
+ Partials      234      49     -185     

Flag	Coverage Δ
integrationtests	68.0% <50.0%> (+0.1%)	⬆️
unittests	86.8% <100.0%> (+2.8%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...src/simcore_service_webserver/storage/_handlers.py	85.9% <100.0%> (+14.8%)	⬆️
...r/src/simcore_service_webserver/storage/_routes.py	100.0% <100.0%> (ø)

... and 632 files with indirect coverage changes

[matusdrobuliak66]

👍

[pcrespov]

I understand that StorageFileID (which is itself a str) is too restrictive, right?

• Why do we define this id?
• If this is not the ID I want for the API, shouldn't you call it AnyFileIDStr instead of StorageFileIDStr?

[GitHK]

If you look at the tests, the incoming string is very closely related to this StorageFileID type. Though, the one incoming has the character "/" url encoded twice.
So I wanted to give an idea that the type should be something related to the original StorageFileID. Also I did not want to break how everything is working at the moment, since this double encoded slash url is generated by the backend, there must be a reason for it.