[Improvement] Use different cURL option to prevent OOM error in collector

A Longhorn user in https://github.com/longhorn/longhorn/issues/5985 noticed that the support bundle collection process could not complete on resource constrained hardware (Raspberry Pi 4s). They found the following in the support bundle agent logs:

+ curl -v -i -H 'Content-Type: application/zip' --data-binary @node_bundle.zip http://10.244.4.60:8080/nodes/w1
curl: option --data-binary: out of memory
curl: try 'curl --help' or 'curl --manual' for more information

This seems to be a known issue with the cURL --data-binary flag. The entire contents of a file are loaded into RAM before the file is sent. A number of (admittedly old) GitHub and StackOverflow issues mention using the -T(--upload-file) option as an alternative.

If it is possible, we should consider using the -T(--upload-file) option to ensure bundles upload successfully even when memory is limited.

https://github.com/curl/curl/issues/1385
https://github.com/curl/curl/issues/290
https://stackoverflow.com/a/69788901

Start by locating the support bundle collector code that builds the curl upload command shown in the agent logs. Check how the node_bundle.zip file is sent, then verify that changing the upload option allows bundles to complete on memory-constrained hardware without the reported out-of-memory error.