Expand rules_python's type checking in CI to apply to remaining code

...where type errors are still prone to getting introduced.

Quoting @aignas in https://github.com/bazel-contrib/rules_python/pull/3240#issuecomment-3384929943
> I personally am not against doing type checking against all of the python code within the repo, but that is a fair amount of work that would definitely benefit from community also pitching in. I'll create a place-holder ticket that is reasonably wide (and we already have a CI job that is doing type checking on the runfiles library), so initially we could use something similar in our initial approach.

首先检查现有的 CI 任务，该任务会对 runfiles 库进行类型检查，并确定仓库中尚未覆盖的其余 Python 代码。当 CI 对这些剩余代码应用类型检查且不引入未解决的类型错误时，工作即完成。

由索引模型根据 Issue 内容生成。