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

Commencez par stdlib/re.pyi, en particulier les définitions de re.match.group* autour des lignes 93–117, et comparez-les avec l’alias MaybeNone dans stdlib/_typeshed/init.pyi. Examinez les cas similaires dans les stubs où cette intention est représentée avec Any ; le travail est terminé lorsque les cas concernés utilisent systématiquement MaybeNone à la place et qu’aucune exception non marquée n’a été trouvée.