Move resource.struct_rusage import

[hauntsaninja]

Fixes #11220

17 iterations of Alex's script and counting...

[hauntsaninja]

Oh no..... on the eighteenth iteration I get:

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/mypy/__main__.py", line 37, in <module>
    console_entry()
  File "/root/.pyenv/versions/3.11.7/lib/python3.11/site-packages/mypy/__main__.py", line 15, in console_entry
    main()
  File "mypy/main.py", line 100, in main
  File "mypy/main.py", line 182, in run_build
  File "mypy/build.py", line 191, in build
  File "mypy/build.py", line 265, in _build
  File "mypy/build.py", line 2943, in dispatch
  File "mypy/build.py", line 3334, in process_graph
  File "mypy/build.py", line 3415, in process_fresh_modules
  File "mypy/build.py", line 2111, in fix_cross_refs
  File "mypy/fixup.py", line 52, in fixup_module
  File "mypy/fixup.py", line 127, in visit_symbol_table
  File "mypy/lookup.py", line 31, in lookup_fully_qualified
AssertionError: Cannot find module for _winapi.ABOVE_NORMAL_PRIORITY_CLASS

I'll get a bigger sample size and see if this is still worth merging

[github-actions]

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

[JelleZijlstra]

At least that's a different import, wasn't it always struct_rusage before?

[hauntsaninja]

I also see struct_rusage in some failures. With larger sample size, I'm not sure that this is any better, but don't think this is any worse. I kind of prefer this aesthetically, so I'm going to merge it and we'll see if it makes any marginal difference.

I'm getting flaky failures going back several months too. My guess is we just shouldn't be invoking mypy in parallel or should be setting --no-incremental or something.

[AlexWaygood]

My current working theory is that there was a latent race condition (due to running many mypys concurrently) that was already present (and has probably always been present since #10714), but was recently made significantly more likely to occur, probably due to our import cycles getting worse