Add "Externally Managed Environments" support to block global package installations via pip

Description:
To prevent system package breakage, many Linux distributions are now restricting pip install to virtual environments or uv environments (something private either way). In self-hosted environments, especially when using ephemeral runners, the hosted tools cache functionality is critical for scaling.

The current methodology allows a pip install to install directly to the cached directory for a given Python after installation, which leads to potentially broken dependency trees and all other kinds of errors if developers are not careful with their package installs. It can also lead to weird race conditions in the same way.

I propose a new input for actions/setup-python that creates the EXTERNALLY-MANAGED file right before a version of Python is marked as available (e.g. creation of the x64.complete file) that would block global pip installs.

https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments

Justification:
Did all of this in the above. Didn't read the template first.

Are you willing to submit a PR?
Absolutely. This is more of a RFC to gauge the level of interest here.

首先阅读用于将已安装的 Python 版本标记为可用的 setup-python tool-cache 路径，然后查看链接的外部管理环境规范。确定在记录可用性之前应如何创建 marker，以及现有的哪些测试覆盖了缓存的 Python 安装。完成标准是：阻止对缓存的解释器执行全局 pip 安装，同时不影响受支持的 virtual-environment 或 uv 工作流。