Fixing typo in cython casting lint, and making it azure friendly
@jbrockmendel 

Fixing typo introduced in #23474, when validating the spaces in casts in the cython code.

The original grep command used was:
`grep -r -E --include '*.pyx' --include '*.pxi.in' '> ' pandas/_libs | grep -v '[ ->]> ' `

If I'm not mistaken, the goal of `grep -v '[ ->]> '` was to exclude from the initially caught `> ` the cases where before the greater than we have a space, a hyphen or another greater than. The problem is that the hyphen is understood as a range, like in `[a-z]`, and the regex is excluding other characters, like the star. So, we're exclusing cases like:
```
pandas/_libs/window.pyx:        buf = <float64_t *> arr.data
pandas/_libs/window.pyx:        oldbuf = <float64_t *> bufarr.data
pandas/_libs/window.pyx:            bufarr.data = <char *> buf
pandas/_libs/window.pyx:        bufarr.data = <char *> oldbuf
```
Which should probably have the same standard as the one we're enforcing.

Just by changing the order of `'[ ->]> '` to `'[ >-]> '` makes it work as expected. But there is an additional problem on this grep. In #22854 I'm moving `code_checks.py` from travis to azure. And I implemented a bash function `invgrep` that is like a grep, that besides inverting the exit status of grep, formats the output in a way that looks nicer in azure. And pipping  two greps together is making things a bit more complex, so I'd prefer to avoid it if possible.

So, the proposed changes in this PR, create a new regex that tries to solve the problem with a single grep. I changed the pattern to match any alphanumberic of star followed by the greater than and the space. But equivalent to what you were doing, we can also use `'[^ ^>^-]> '`. Happy to change to it if it makes more sense to you.

If you can confirm that my assumptions are correct, I'll fix the pending cases in this PR, so the CI is green and we can merge.