ci: start minio as first step

[trim21]

avoid flaky test

  1) functional tests
       "before all" hook in "functional tests":
     S3Error: Server not initialized, please try again.
      at Object.parseError (src\/xml-parsers.js:37:11)
      at parser (src\/transformers.js:121:22)
      at Transform._flush (src\/transformers.js:51:12)
      at Transform.prefinish (node_modules\readable-stream\lib\_stream_transform.js:123:10)
      at Transform.emit (node:events:511:28)
      at prefinish (node_modules\readable-stream\lib\_stream_writable.js:569:14)
      at finishMaybe (node_modules\readable-stream\lib\_stream_writable.js:576:5)
      at endWritable (node_modules\readable-stream\lib\_stream_writable.js:594:3)
      at Transform.Writable.end (node_modules\readable-stream\lib\_stream_writable.js:535:22)
      at IncomingMessage.onend (node:internal/streams/readable:713:10)
      at Object.onceWrapper (node:events:625:28)
      at IncomingMessage.emit (node:events:523:35)
      at endReadableNT (node:internal/streams/readable:1367:12)
      at processTicksAndRejections (node:internal/process/task_queues:82:21)

[trim21]

@aldy505 minio:edge-cicd is too old and minio doesn't have a windows native docker image. Using docker image is not possible on windows, even latest or edge tag.

[prakashsvmx]

LGTM 👍

[aldy505]

@aldy505 minio:edge-cicd is too old and minio doesn't have a windows native docker image. Using docker image is not possible on windows, even latest or edge tag.

@trim21 regarding that, I'd actually wanted to suggest the minio team to create that image on each release (or on the main branch). Personally, I have an image to do that: https://github.com/aldy505/continuous-integration-images/blob/master/minio/Dockerfile But I don't think it's something that's good to use here.