Allow to throw OpenEoApiError with message as positional argument

[EmileSonneveld]

Detail, but in this code, it is assumed that any exception takes the message as the first positional argument:

            # Re-raise with enriched message while preserving original exception type and details
>           raise type(e)(f"{str(e)}{debug_info}") from e
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E           TypeError: OpenEoApiError.__init__() takes 1 positional argument but 2 were given

openeo-geopyspark-integrationtests/tests/test_integration.py:135: TypeError

This happened in this integration tests.

[soxofaan]

I think the problem here lies in that type(e)(f"{str(e)}{debug_info}") construction, not in the OpenEoApiError implementation: it assumes that all constructors only accept one positional argument for the message, which is risky.

For example : #895 won't fix the problem: just making message a positional argument is not enough, OpenEoApiError has additional required arguments http_status_code and code, so type(e)(f"{str(e)}{debug_info}") will still fail

[EmileSonneveld]

True, I ran the test again with an explicit throw and got this error:
E TypeError: OpenEoApiError.__init__() missing 2 required keyword-only arguments: 'http_status_code' and 'code'

When just attaching the debug info to the existing error instead of making a new one, I got nicer looking logs:

        with job_context(job):
>           raise OpenEoApiError("test", http_status_code=500, code="code")
E           openeo.rest.OpenEoApiError: [500] code: test
E           ============================================================
E           JOB DEBUG INFORMATION
E           ============================================================
E           Job ID: j-2605080932234edd96c6bbd4b209b67a
E           Job Status: queued
E           Job Error Logs:
E           ============================================================

[EmileSonneveld]

Reverted python client MR