Use bool | Literal[0, 1] instead of int in some tkinter bool parameters

[Akuli]

This is a less disruptive version of #11394.

In general, passing 0 or 1 is less readable and just not the right thing to do in new code. Users should just use the new and readable thing instead of the confusing legacy thing. Tkinter (and much of its documentation) was created before bool was added to Python.

That said, there's still plenty of example code around (e.g. stackoverflow answers, tkinter docstrings) that use 0 and 1. IMO we should apply Literal[0, 1] to tkinter booleans only when someone needs it in a specific place, not blindly to all boolean parameters.

This is also why I don't want yet another type alias, e.g. _TkBool = bool | Literal[0, 1]. In most cases, it's not the right thing to use, so I don't want a convenience thing for it.

[github-actions]

According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉