Pass custom pipeline error logging for "failed" Pipeline loads -- not clear why it failed.

[ventz]

It would be helpful to have better error logging for when pipeline fails to load a custom Pipeline.

If a custom Pipeline fails to load and gets moved to "failed", it is not clear what caused it as nothing is logged/the error is not passed.

Ex:

pipelines-1  | PIPELINES_REQUIREMENTS_PATH not specified. Skipping installation of requirements.
pipelines-1  | Download + install Executed in mode: full
pipelines-1  | RESET_PIPELINES_DIR is not set to true. No action taken.
pipelines-1  | PIPELINES_REQUIREMENTS_PATH not specified. Skipping installation of requirements.
pipelines-1  | PIPELINES_URLS not specified. Skipping pipelines download and installation.
pipelines-1  | Running via Mode: full
pipelines-1  | INFO:     Started server process [7]
pipelines-1  | INFO:     Waiting for application startup.
pipelines-1  | WARNING:root:No Pipeline class found in <custom-name>.
pipelines-1  | INFO:     Application startup complete.
pipelines-1  | INFO:     Uvicorn running on http://0.0.0.0:9099 (Press CTRL+C to quit)

In this case for example, it was a missing comma:

File "/app/pipelines/<custom-name>.py", line 117
    ...error...
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?