Rudder

Today, we have two different syntax to use Rudder global parameter:

- when used in technique or ncf, we must use: ${rudder_parameters.PARAM_NAME},
- when used in directive, we must use: ${rudder.param.PARAM_NAME}.

We must use the same syntax for both case, and provide a migration script that will go trought all instances of used one to change it to the new syntax.

The new syntax should be align with the one provided for node properties, see: #9057

So we could have something like: ${rudder.parameters[PARAM_NAME]. That would also help allowing to add JSON support in these parameters. And if we go that way, we will also add "node" and "default" option (but perhaps restricted somehow, the question being: does we want to tell user that a global param may have a default from a for example node properties (nothing stop it technically)).

And finally, we will most likelly also normalise ${rudder.node.(hostname, id, etc)} and ${rudder.node.policyServer.(hostname, id, etc)} with the same rules, and perhaps behind an other root ${node.info} (and have after a ${node.inventory} etc)