Add notes to `ImportError` for common issues

Feature or enhancement

Proposal:

ImportErrors are very common, and almost always dependent on the interpreter initialization and/or environment setup. There are many common issues we could try to detect, and give users hints on the possible cause.

• Failing to load native modules when a module for a different ABI is available
  • Eg. https://github.com/python/cpython/issues/127294#issuecomment-2501787837
    • A .cp313t-win_amd64.pyd module is available, but we were looking for .cp313-win_amd64.pyd
• Failing to import a non-stdlib module with the site initialization disabled (-S)
• Failing to import a module available in the user site-packages with the user site initialization disabled (-s)
• Failing to import a module available in . with PYTHONSAFEPATH/-P enabled
• Failing to import a module when ignoring PYTHON* environment variables (-E) but PYTHONPATH or PYTHONHOME are set (which users might be relying on)
• (suggest more!)

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

• gh-136817
• gh-136821

No source files or tests are named in the issue. Review linked PRs gh-136817 and gh-136821 first, then trace the ImportError handling relevant to the selected environment cases; done means adding and testing helpful notes for the agreed cases.