`ERR_API_DEPLOYER_STATIC_ACTIVATE_FAILED` should surface code environment build errors

Tanguy

Context

When deploying an API service via the API Deployer (static infra), if the code environment fails to build on the API node, the Deployer UI shows this:

The problem

This error message gives zero indication that the root cause is a code environment build failure (in our case, a pip install failing due to an incompatible package version on Python 3.11). We had to SSH into the API node and manually dig through apimain.log to find the actual pip traceback.

Additionally, the error code ERR_API_DEPLOYER_STATIC_ACTIVATE_FAILED is not documented in the
https://doc.dataiku.com/dss/latest/troubleshooting/errors/index.html , which makes debugging even harder.

Suggestion

1. When activation fails due to a code env build error, the Deployer UI should explicitly say so (e.g., "Code environment build failed on the API node")
   and include the pip error output — this information is already available in the API node logs
2. Document ERR_API_DEPLOYER_STATIC_ACTIVATE_FAILED in the troubleshooting reference, with common causes (code env build failure, incompatible packages, etc.)

This would save significant debugging time: the fix itself was trivial (updating a pandas version constraint), but finding the cause required direct access to the API node (which the user facing the problem didn't have).

Note: DSS version in the above picture was 13.4.1