Don't set content-type header on finding upload

Some system seem to be using these in their signiture checks

Minio: Doesn't check
DigitalOcean: Doesn't check
GCP: Does check

Author: J12934

parser-sdk/nodejs/parser-wrapper.js

@@ -89,25 +89,27 @@ async function main() {
 
   console.log(`Uploading results to the file storage service`);
 
-  await axios.put(resultUploadUrl, findingsWithIds).catch(function(error) {
-    if (error.response) {
-      // The request was made and the server responded with a status code
-      // that falls out of the range of 2xx
-      console.error(
-        `Finding Upload Failed with Response Code: ${error.response.status}`
-      );
-      console.error(`Error Response Body: ${error.response.data}`);
-    } else if (error.request) {
-      console.error(
-        "No response received from FileStorage when uploading finding"
-      );
-      console.error(error);
-    } else {
-      // Something happened in setting up the request that triggered an Error
-      console.log("Error", error.message);
-    }
-    process.exit(1);
-  });
+  await axios
+    .put(resultUploadUrl, findingsWithIds, { headers: { "content-type": "" } })
+    .catch(function(error) {
+      if (error.response) {
+        // The request was made and the server responded with a status code
+        // that falls out of the range of 2xx
+        console.error(
+          `Finding Upload Failed with Response Code: ${error.response.status}`
+        );
+        console.error(`Error Response Body: ${error.response.data}`);
+      } else if (error.request) {
+        console.error(
+          "No response received from FileStorage when uploading finding"
+        );
+        console.error(error);
+      } else {
+        // Something happened in setting up the request that triggered an Error
+        console.log("Error", error.message);
+      }
+      process.exit(1);
+    });
 
   console.log(`Completed parser`);
 }