fix(storage): re-throw upload error after aborting in uploadFileInChunks

[thiyaguk09]

Description

Ensures TransferManager.uploadFileInChunks always rejects with a MultiPartUploadError when a multipart upload fails, even when automatic cleanup (abortUpload) succeeds.

Impact

Prevents silent data loss where failed chunked uploads previously resolved to undefined after aborting the multipart upload, misleading callers into assuming the file upload succeeded.

Changes

• Removed the early return; statement in uploadFileInChunks after mpuHelper.abortUpload() succeeds so that the original upload error is thrown as a MultiPartUploadError.
• Preserved both the original upload error message and the abort error message when mpuHelper.abortUpload() also fails.

Testing

• Updated the existing abortUpload unit test in test/transfer-manager.ts to assert that uploadFileInChunks rejects with the original upload error when abortUpload succeeds.
• Added a unit test in test/transfer-manager.ts verifying that when both uploadPart and abortUpload fail, the rejected MultiPartUploadError includes both error messages.

Fixes #9193

[gemini-code-assist]

Code Review

This pull request updates the error handling in TransferManager during multipart upload failures, ensuring that if aborting the upload also fails, a MultiPartUploadError combining both the original error and the abort error is thrown. Unit tests have been updated and added to verify this behavior. Feedback suggests a more defensive approach to extracting error messages from the caught exceptions to avoid potential runtime TypeErrors if the thrown values are not standard Error objects.

[kalragauri]

The PR description contains file:///usr/local/google/home/thiyaguk/... links in the raw markdown that do not render as working links on GitHub. These local file:// URLs will also be recorded permanently in the commit message.

Consider replacing the file:// links with actual file paths.

[thiyaguk09]

The PR description contains file:///usr/local/google/home/thiyaguk/... links in the raw markdown that do not render as working links on GitHub. These local file:// URLs will also be recorded permanently in the commit message.

Consider replacing the file:// links with actual file paths.

updated.