second degree callback parameter detection

This came up when discussing https://github.com/Open-EO/openeo-geotrellis-extensions/issues/154 with @EmileSonneveld :

example snippet had something like:

cube = cube.apply_dimension(
    dimension="t", 
    process=lambda data: data.array_apply(lambda foo: foo + 1)
)

Note 2 orders of callbacks: array_apply(...) in apply_dimension and foo+1 in array_apply

Client creates process graph, where the array_apply process looks like:

                    "add1": {
                      "process_id": "add",
                      "arguments": {
                        "x": {
                          "from_parameter": "foo"
                        },
                        "y": 1
                      },

Note the "from_parameter": "foo", which should be "from_parameter": "x"

Start by tracing callback parameter detection from apply_dimension into the nested array_apply callback shown in the example. Reproduce the generated process graph and verify that the inner foo reference is emitted as from_parameter "x" rather than "foo".