Pass environment to ad-hoc actions

This blueprint suggest to pass the environment to ad-hoc cations in a similar way it passes to inner workflows.
A user can pass an environment to a workflow execution and the environment passes to any workflow that is triggered in the executions of the tasks in the workflow.

mistral cli call to pass environment to a workflow:
mistral execution-create my_wf wf_inputs.json params.json

params.json include the environment.
example:
{
 "env": {
  "url": "http://requestb.in/u7rgsr",
  "X_Auth_Token": "8450ffff9e0e4e72bb89b3088aa340b1"
 }
}

A user can access an ad-hoc action with the next mistral yaql expression: <% env() %>

Today the only way to pass the environment to an ad-hoc action is explicitly, as an input.