Generic `Connection.process()`?

[soxofaan]

While the python client provides a lot of helpers/convenience functions/methods for standard openEO processes, there is sometimes need for generally "starting" a process graph from some non/less-standard openEO process (e.g. user defined processes or remote process definitions).
For that, we currently have Connection.datacube_from_process() (with some variants).

This helper dates back from 2020 (9db6452), when DataCube was roughly the only process graph abstraction/wrapper in the client. Since then however quite some other variants were added, like vectorcube, mlmodel, stac_resource, etc.
This makes datacube_from_process() insufficient:

• its name refers to datacube, while it should be about other types too
• it should return the correct wrapper based on the openEO process return type

I'm considering to add Connection.process() to handle this, but a bit hesitant, because "process" as name is quite generic, and can lead to confusion: does it refer to the noun process or the verb? Does calling it trigger processing (e.g. like there is already Connection.execute()) or is it just about building a process graph?

related issues:

• export_workspace not possible when running UDP with datacube_from_process #844
• Use run_udf to run CWLs openeo-geopyspark-driver#1476 (comment)