Windows filename sanitizer misses Unicode COM/LPT reserved device names

I found a way for a server-selected Windows filename to bypass curl's reserved DOS device-name sanitizer. With `curl -O -J`, a `Content-Disposition` filename such as `COM¹`, `COM²`, `COM³`, `LPT¹`, `LPT²`, or `LPT³` is left unchanged, even though Windows treats all six as reserved device names.

(curl_strnequal(p, "COM", 3) || curl_strnequal(p, "LPT", 3)) ?
  (('1' <= p[3] && p[3] <= '9') ? 4 : 3) : 0;