Add helpful warning for invalid file pattern for Windows users

[hudochenkov]

What is the problem you're trying to solve?

Users on Windows sometimes have problems to start using stylelint, because of invalid CLI file name pattern params. E. g., #3624.

What solution would you like to see?

I believe we can detect invalid quotes in a file pattern for Windows users, and show a warning with a correct example.

Example for CLI:

$ stylelint './file.css'

  Please, use double quotes for a file pattern:

      stylelint "./file.css"

Example for npm script:

{
    "scripts": {
        "lint:css": "stylelint './file.css'"
    }
}

$ npm run lint:css

  Please, use escaped double quotes for a file pattern in your npm scripts:

      stylelint \"./file.css\"

I don't know if it's possible to do the second one, but the first one is quite doable.

[jeddy3]

SGTM. I think anything that improves the DX is a good thing.

[github-actions]

This issue is older than one month. Please ask before opening a pull request, as it may no longer be relevant.