[SonataFlow] Upgrade the Knative custom functions to have visibility over the returned status code and headers

[oEscal]

Description

This feature is to expand feature #3936 to Knative custom functions.

Implementation ideas

Since Knative custom functions have their specific way of defining the function properties, fail_on_status_error, return_headers, and return_status_code must be defined within the operation parameters. Therefore, considering the current parameters nomenclature style, they can be named as follows: failOnStatusError, returnStatusCode, and returnHeaders.
An example of how to use them:

  "functions": [
    {
      "name": "greet",
      "type": "custom",
      "operation": "knative:services.v1.serving.knative.dev/custom-function-knative-service?failOnStatusError=false&returnStatusCode=true&returnHeaders=false"
    }
  ]

[ricardozanini]

@oEscal are you going to merge both issues in the same PR?

[oEscal]

@ricardozanini No, I only did it like this because this feature required the other two:

• It needed the Knative headers functionality to be able to redirect the response headers from one response to the request of the following one
• Regarding the REST custom function feature, it inherits that functionality from the code I made in that PR.

In any case, my idea is that the other two functionalities would be merged first before this one :)