Deprecate imports when installation has started

[notatallshaw]

Towards #13828

Uses the addaudithook approach to what was suggested in the DPO thread on the problems with globally disabling PEP 810 style lazy imports, but had to be expanded a little as various nuances where found while testing.

[notatallshaw]

This approach has a reasonable chance of breaking tools which manipulate pip such as pip-tools, and possibly redistributions of pip. If we agree this is the correct approach we should contact Linux distributions and known tools that are coupled to the internals of pip and see what could be done to make it less likely to break or give configuration options.

[notatallshaw]

This approach has a reasonable chance of breaking tools which manipulate pip

I've taken the approach I discuss in #13828 (comment) and turned this into a depreciation which makes it significantly safer to roll out.

[ichard26]

This is 100% a drive-by review since I have zero free time, but FWIW, if we're going with a warning initially, I'd want the call stack to be printed (or a truncated one, at least) so we can easily identify where these imports are happening.

[notatallshaw]

I'd want the call stack to be printed (or a truncated one, at least) so we can easily identify where these imports are happening.

The file and line number that caused the warning is now included.

[notatallshaw]

I have no idea how/why this PR got merged, I am reverting and then creating a new clean PR.

[notatallshaw]

#13912