@uppy/aws-s3: console.error instead of throw for missing etag

[Murderlon]

Closes #5516

[github-actions]

Diff output files

diff --git a/packages/@uppy/aws-s3/lib/index.js b/packages/@uppy/aws-s3/lib/index.js
index e312727..88fd867 100644
--- a/packages/@uppy/aws-s3/lib/index.js
+++ b/packages/@uppy/aws-s3/lib/index.js
@@ -501,15 +501,13 @@ export default class AwsS3Multipart extends BasePlugin {
           location,
         } = headersMap;
         if (method.toUpperCase() === "POST" && location == null) {
-          console.warn(
-            "AwsS3/Multipart: Could not read the Location header. This likely means CORS is not configured correctly on the S3 Bucket. See https://uppy.io/docs/aws-s3-multipart#S3-Bucket-Configuration for instructions.",
+          console.error(
+            "@uppy/aws-s3: Could not read the Location header. This likely means CORS is not configured correctly on the S3 Bucket. See https://uppy.io/docs/aws-s3/#setting-up-your-s3-bucket",
           );
         }
         if (etag == null) {
-          reject(
-            new Error(
-              "AwsS3/Multipart: Could not read the ETag header. This likely means CORS is not configured correctly on the S3 Bucket. See https://uppy.io/docs/aws-s3-multipart#S3-Bucket-Configuration for instructions.",
-            ),
+          console.error(
+            "@uppy/aws-s3: Could not read the ETag header. This likely means CORS is not configured correctly on the S3 Bucket. See https://uppy.io/docs/aws-s3/#setting-up-your-s3-bucket",
           );
           return;
         }