Document the The system cannot find the path specified error in windows

[mkumatag]

While running the following command on the Windows platform, failed to find the file on that

 ./pvsadm image upload --bucket bucket-validation-team --file /tmp/tmp.2iM2Ph53Ls/test --bucket-region us-south --resource-group ocp-validation-resource-group
I1215 07:55:48.582771   14036 root.go:29] Using an API key from IBMCLOUD_API_KEY environment variable
I1215 07:55:59.301186   14036 upload.go:81] Found bucket bucket-validation-team in the cos-validation-team instance
I1215 07:55:59.301186   14036 s3client.go:130] uploading the object /tmp/tmp.2iM2Ph53Ls/test
Error: err opening file /tmp/tmp.2iM2Ph53Ls/test: open /tmp/tmp.2iM2Ph53Ls/test: The system cannot find the path specified.
Usage:
  pvsadm image upload [flags]
Flags:
      --resource-group string      Name of user resource group. (default "default")
      --cos-storageclass string    Cloud Object Storage Class type, available values are [standard, smart, cold, vault]. (default "standard")
  -n, --cos-instance-name string   Cloud Object Storage instance name.
  -b, --bucket string              Cloud Object Storage bucket name.
  -f, --file string                The PATH to the file to upload.
  -r, --bucket-region string       Cloud Object Storage bucket region. (default "us-south")
  -h, --help                       help for upload
Global Flags:
      --add_dir_header                   If true, adds the file directory to the header of the log messages
      --alsologtostderr                  log to standard error as well as files
  -k, --api-key string                   IBMCLOUD API Key(env name: IBMCLOUD_API_KEY)
      --audit-file string                Audit logs for the tool (default "pvsadm.log")
      --debug                            Enable PowerVS debug option(ATTENTION: dev only option, may print sensitive data from APIs)
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory
      --log_file string                  If non-empty, use this log file
      --log_file_max_size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --logtostderr                      log to standard error instead of files (default true)
      --one_output                       If true, only write logs to their native severity level (vs also writing to each lower severity level
      --skip_headers                     If true, avoid header prefixes in the log messages
      --skip_log_headers                 If true, avoid headers when opening log files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
  -v, --v Level                          number for the log level verbosity
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
E1215 07:55:59.311261   14036 root.go:68] err opening file /tmp/tmp.2iM2Ph53Ls/test: open /tmp/tmp.2iM2Ph53Ls/test: The system cannot find the path specified.
Administrator@frenulum1 /cygdrive/c/users/Julie
$ ls -l  /tmp/tmp.2iM2Ph53Ls/test
-rw-r--r-- 1 Administrator None 0 Dec 15 06:54 /tmp/tmp.2iM2Ph53Ls/test

This is because this command is running in the cygwin environment and the actual path of the file located in <cygwin_path>/tmp/XXXXX, hence need documentation about how to use this in windows.

/kind documentation /priority important-soon