doc and various fixes of lua for windows

doc/manual/sphinx/source/test_items/lua_func_test_item.rst

@@ -62,4 +62,25 @@ on how to access to global variables from test items and scripts).
 
 In the example above, the global variable ``$(lfn_activity)``
 would be created at the end of the item execution. It would contain the resulting
-value of the funcToBeExecuted python function.
+value of the funcToBeExecuted python function.
+
+**Global variables**
+
+Some global variables have an impact on the ``lua_func`` test item behavior:
+
+* ``lua_path``: This optional global variable can be used to define
+  the lua executable path. If not defined, the lua interpreter is
+    searched in at the default place in the system.
+* ``lua_env``: This global variable can be used to define
+  environment variables for the lua script execution environment.
+  Only `PATH`, `LUA_PATH`, and `LUA_CPATH` are supported.
+
+  .. code-block:: yaml
+      :caption: example of configuration file: param.yaml
+
+      [...]
+      lua_env:
+        PATH: "/my/path/"
+        LUA_PATH: "/my/lua/modules/?.lua;;"
+        LUA_CPATH: "/my/lua/modules/?.so;;"
+      [...]

doc/manual/sphinx/source/test_items/py_func_test_item.rst

@@ -105,4 +105,12 @@ on how to access to global variables from test items and scripts).
 
 In the example above, the global variable ``$(pfn_function test item)``
 would be created at the end of the item execution. It would contain the resulting
-value of the funcToBeExecuted python function.
+value of the funcToBeExecuted python function.
+
+**Global variables**
+
+Some global variables have an impact on the ``py_func`` test item behavior:
+    
+* ``python_path``: This optional global variable can be used to define
+  the python executable path. If not defined, the python interpreter is
+  searched in at the default places in the system.