Replace `float` with `float | int`

As discussed in python/typing#1748: I propose to (slowly) replace float with float | int and complex with complex | float | int, where applicable.

• It's more correct, even if float is current implicitly equivalent to int | float.
• We are already prepared should the implicit promotion ever be removed.
• We give type checkers the ability to optionally disable the promotion so that type checker authors and users can experiment with it.
• Typeshed would always need to be the first step for this, so let's remove this blocker.

This issue proposes an ugly and slow, but correct and safe procedure:

1. Disable flake8-pyi code Y041.
   #16096
2. Introduce two type aliases FloatInt = float | int and ComplexInt = complex | float | int to _typeshed.
   #16068
3. Globally replace all instances of float with FloatInt and of complex with ComplexInt in the stdlib.
4. After 2026-09-22 we do the same for third-party stubs.
5. Review FloatInt and ComplexInt instances are replace them with the proper types. (This will take a while.)
6. Remove the type aliases once they are not needed anymore (in 10 years or so ...)

Using FloatInt and ComplexInt would be disallowed for new code and the type aliases should explicitly be marked as not to be used by non-typeshed code.

We should also probably add flake8-pyi checks that checks that argument types use float | int and complex | float | int. Cases where only float/complex is allowed are probably rare.

stdlib のスタブと _typeshed の FloatInt および ComplexInt エイリアスから始め、次に flake8-pyi の Y041 設定を確認します。stdlib 全体で float および complex のアノテーションを検索し、各候補を確認します。完了とは、計画されている stdlib 全体の移行を意味し、サードパーティ製スタブは 2026-09-22 まで保留されます。