Parse urlencoed URI paths

[mateuszkj]

Describe the bug
URI paths from HTTP request should be urldecoded.

To Reproduce

1. Create example data and run S3 server

mkdir -p example/data
echo "abc" >  example/data/abc=1.txt
RUST_LOG=debug s3-server --fs-root ./example/

2. Get file by curl

$ curl -i "http://localhost:8014/data/abc%3D1.txt"
HTTP/1.1 404 Not Found
content-type: text/xml
content-length: 127
date: Sat, 09 Apr 2022 22:40:02 GMT

<?xml version="1.0" encoding="UTF-8"?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message></Error>

Expected behavior

$ curl -i "http://localhost:8014/data/abc%3D1.txt"
HTTP/1.1 200 OK
last-modified: Sat, 09 Apr 2022 22:35:00 GMT
content-length: 4
etag: "0bee89b07a248e27c83fc3d5951213c1"
date: Sat, 09 Apr 2022 22:40:45 GMT

abc

Additional context

Client https://crates.io/crates/rust-s3 urlencodes special characters, so this merge requests fixes it.

[Nugine]

Thank you for the fix.
There are some lines to be changed. And then we can merge this PR.

[mateuszkj]

@Nugine thanks for core review. I have applied yours comments and force pushed.