Improve evaluate_paramenter_dict exceptions error message

[FelipeGdM]

This PR updates the evaluate_paramenter_dict() possible exceptions adding the name of the parameter that caused the exception, thus helping find the root of the problem when it occurs

For example, if a NoneType argument is passed to the function, the thrown message would be

TypeError: Allowed value types are bytes, bool, int, float, str, Sequence[bool], Sequence[int], 
Sequence[float], Sequence[str]. Got <class 'NoneType'>. If the parameter is meant to be 
a string, try wrapping it in launch_ros.parameter_descriptions.ParameterValue(value, value_type=str)

Within a large project, with dozens of launch arguments, it is not trivial to discover which argument received the invalid value. As the name of the argument being evaluated is already available in the scope of the exception, adding it to the error message would be really helpful when dealing with this problem.

As discussed in some ROS 2 tickets (#291, ros2/launch#412), one of the main issues of the launch system is the lack of helpful information when something goes wrong, this PR is a small step in the direction of solving this issue

[methylDragon]

• Linux
• Linux-aarch64
• Windows