Set up ty in CI
Hello,

This PR sets up [`ty`](https://github.com/astral-sh/ty), a type checker developed by the creator of `ruff`, in CI.

I'm aware that `ty` is still in preview but there can be a couple of benefits in adding it now. 
- It's already very fast and can help us debug faster. `mypy` is quite slow and disrupts the coding flow.
- The cost of setup is pretty cheap, as it's mostly similar to `mypy` and `pyright`. Currently I ignore all errors so that we can fix and enable them gradually, like the other linting and typing errors.
- This also allows us to evaluate if/when `ty` can be a replacement of `mypy` and `pyright`.

Let me know what you think.

- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Thanks for the PR but closing until ty is more matrue