[feat] Downloads/Uploads manager usage simplification and sample unification

[matejmolnar]

This PR aims to simply the usage of DownloadAPIManager/UploadAPIManager and also unify the sample screens logic + UI.

Managers usage simplification

While I was writing a new README I realised that we are forcing the user to create unnecessary Router boiler plate in order to create a download/upload request.

Download

Hence I've created a new method on DownloadAPIManaging where you can simply pass the URL of the file you wish to download instead of Requestable. The request is then made with internal dummy DownloadRouter.

    func downloadRequest(
        _ fileURL: URL,
        resumableData: Data? = nil,
        retryConfiguration: RetryConfiguration? = .default
    ) async throws -> DownloadResult {
        try await downloadRequest(
            DownloadRouter(fileURL: fileURL),
            resumableData: resumableData,
            retryConfiguration: retryConfiguration
        )
    }

Upload

First I've created a new enum UploadType and I replaced the three different upload methods with one where you pass an uploadType parameter. Then I defined a new method where you can pass the UploadType and an upload URL. Similarly to download the request is made with internal dummy UploadRouter.

    func upload(_ type: UploadType, to uploadURL: URL) async throws -> UploadTask {
        try await upload(type, to: UploadRouter(url: uploadURL, uploadType: type))
    }

Sample logic + UI unification

• Create UploadAPIManager shared instance.
• Remove UploadService and use the shared manager instance instead.
• Remove FormUploadsViewModel and move the logic to the UploadsViewModel.
• Create new TaskProgressView with generic viewModel of TaskProgressViewModel protocol and use it in both upload and download screens.

[cejanen]

We're almost there. I think about few little improvements we can do here.

[cejanen]

🩴

[cejanen]

it took me only ages but at the end I'm happy with result
📲

[gajddo00]

🐱