Consistently mark types with `| MaybeNone` whenever it is applicable

I noticed that there's a special type alias MaybeNone that represents this specific intent:

We didn't dare to change the type to X | None so instead we changed it to Any

You can find an example in a relatively recent addition of this.

And while this approach makes me very sad, it is good that such cases are marked with MaybeNone, for the purpose of looking at them specially. Maybe some type checker will arise that will have specific handling for it and do something smarter instead.

With that in mind, it would be good to ensure that all such cases are consistently marked.

I noticed at least one case that is not marked like this. It has | Any directly written instead of | MaybeNone. This is in re.match.group*:

https://github.com/python/typeshed/blob/6feca188689e14cdacd8dbf8bc9cf0635993027a/stdlib/re.pyi#L93-L117

stdlib/re.pyi から始め、特に 93–117 行付近の re.match.group* 定義を確認し、stdlib/_typeshed/init.pyi の MaybeNone エイリアスと比較してください。これと同じ意図が Any で表現されている stubs 内の類似ケースを確認してください。該当するケースが一貫して代わりに MaybeNone を使用し、マークされていない例外が見つからなければ完了です。