feat: Copy free upload

[LouisCAD]

Now, the app starts a foreground service as soon as user-picked files arrive in the app.

That way, we can keep the URI permissions until the upload is complete, without having to import/copying the data into the app storage.

That lets us avoid filling the user device, and avoids no free storage issues.

Change operations:

1. Replace DB-backed upload session with in-memory UploadState
2. Replace UploadWorker with UploadForegroundService
3. Replace UploadFileTask with TransferUploader
4. Replace TransferSendManager with UploadSessionStarter
5. Replace ImportFilesScreen with PickFilesScreen
6. Replace ImportFilesViewModel with PickFilesViewModel
7. Merge all upload related screen (progress, errors, success, email validation…)
8. Simplify navigation
9. Remove ImportationFilesManager
10. Remove ImportLocalStorage
11. Ensure the old importation directory is removed if present, freeing storage
12. Extract a few classes into their own file
13. Update NotificationUtils code for naming semantics

Depends on Infomaniak/android-core#305

[github-actions]

This PR/issue depends on:

• feat: Add ForegroundService API, and other extensions, needed for copy-free-upload android-core#305
  By Dependent Issues (🤖). Happy coding!

[LouisCAD]

Things to do in this PR, or after:

• Thumbnails:
  • Save thumbnails during the upload, as was done in https://github.com/Infomaniak/android-SwissTransfer/pull/414/files
• Implement upload cancellation with a worker
  • Think through retries backoff and hard limit for giving-up.
• Change notification wording from "draft" to "pending"
• Check BackHandlers of UploadScreen and nested composables don't clash
• Think through the canRetry in the notification, we might want a more precise error message (reuse the one shown in the app?)
• Check the notification message stays consistent across updates

Things to do definitely after:

• Extract stuff from UploadForegroundService's companion object.

For the android-core repo:

• Move ForegroundService into its own module and add the android.permission.FOREGROUND_SERVICE for older Android versions.
• Add @RequiresPermission for withPartialWakelock

[sirambd]

Don't forget to reformat all files, and group properties at the top of files

[sirambd]

Add a translated string

[LouisCAD]

Done, reused the one shown in the bottom sheet. That said, I think we should think through this redundancy.

If we show a bottom sheet, what are supposed to show in the screen below?
If we show the error below, do we need a bottom sheet in the first place?

Also, do we allow retrying somehow, in case the user leaves a restricted location?

[sirambd]

Check this canRetry because it's always true

[LouisCAD]

Noted in my comment above. Maybe check that after this PR?

[LouisCAD]

I did my best to address everything in new commits (without touching the previous ones since your review, @sirambd).

I hope it's good to go, and that we can do what I wrote down in the updated comment above after.

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
11 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[LouisCAD]

BTW, about notifications, we need to allow the upload to start even if the permission is denied.

Foreground services can still run without that, so we don't absolutely need it to proceed with the transfer upload.

We probably want an alternative to guardedCallback { …} that gets called whatever the permission grant result is (but still after we receive the result). Maybe a name like a requestingCallback { … } extension for the permission state.