feat(storage_client): upload signed URL

[dshukertjr]

What kind of change does this PR introduce?

Implements signed upload URL by adding Expose the createUploadSignedUrl, uploadToSignedUrl, and uploadToSignedUrl methods. This allows developers to first upload the file to their own server while attaching the token from createSignedUploadUrl() method, and then complete the upload process from their server to Supabase.

final response =
    await storage.from(newBucketName).createSignedUploadUrl(uploadPath);

// Uploads the file to their own server, and call the following to complete the upload to Supabase

await storage
    .from(newBucketName)
    .uploadToSignedUrl(response.path, response.token, file);

I didn't add the binary version of uploadToSignedUrl method, as it is intended to be used in a server environment.

Related supabase/storage-js#158, supabase/storage#282 (comment)

[Vinzent03]

I didn't add the binary version of uploadToSignedUrl method, as it is intended to be used in a server environment.

dart_edge for example runs on the server, but compiles Dart to js, so File won't work. I would binary as well.

[dshukertjr]

@Vinzent03
Sure, thanks for the suggestion! I know you only had good intentions, but I might appreciate it if you could wait on commenting on PRs until they are out of the draft status.

[Vinzent03]

So far we are using (response as Map)['Key'] as String to return the path in upload(), but I see that storage-js uses cleanPath everywhere. I guess they are always the same, so it doesn't matter.

[bdlukaa]

Isn't it possible to make retryAttempts non nullable?

int retryAttempts = 0,

[dshukertjr]

Oh yeah, giving it a default value would be so much better!

[dshukertjr]

Actually, I just remembered. There is a global settings for retryAttempt, and if the retryAttempt value passed to the individual methods are null, it will fall back to the global default, so we might need to keep it nullable here.

[bdlukaa]

Can't we use the new super constructors?

Suggested change

	const SignedUploadURLResponse({
	required String signedUrl,
	required String path,
	required this.token,
	}) : super(
	signedUrl: signedUrl,
	path: path,
	);
	const SignedUploadURLResponse({
	required super.signedUrl,
	required super.path,
	required this.token,
	});

[dshukertjr]

That's a great point. Currently, the minimum Dart SDK version is 2.15.0, and I believe the new super constructor was introduced on v2.17.0, so let's actually do that in another PR. I think we can bump the minimum SDK version to 2.17.0 and minimum Flutter version to 3.0.0 soon, since it's been a while for those to be around.

[Vinzent03]

Isn't it better to add the documentation to the field itself and not just to the class? So that for example vscode can show the doc on path when using signedUrl.path.

[dshukertjr]

@Vinzent03
Yeah, I don't know what I was thinking 😂