Line number in config error message

Short description of the MR

Line number of yaml file included in configuration error message

Examples: 1.

24: data:
25:   type: array
26:   subtype: duoble
27:   size: [10, '$psize[0]*($dsize[0]-2)', '$psize[1]*($dsize[1]-2)']

Log:

[PDI][NOINIT] *** Fatal error: Config_error in line 26: Unknown data type: `duoble

35: dataset_selection: # only write into a single slice in time
36:   size:  ['$dsize[0]-2', '$dsize[1]-2']
37:   start: [$iter, '($dsize[0]-2)*$pcoord[0]', '($dsize[1]-2)*$pcoord[1]']

Log:

[PDI][000002][15:09:41] *** error: Error while triggering data share `main_field': Config_error in line 36: Invalid selection: 2 selection in 3 array

18: plugins:
19:   set_value:
20:     on_data:
21:       main_field:
22:         expose:
23:           iter: 1

Log:

[PDI][NOINIT] *** Fatal error: Config_error in lines 22 - 23: Operations must be defined as a list

List of things to check before making a MR

Before merging your code, please check the following:

• you have added a line describing your changes to the Changelog;
• you have added any new or changed yaml config format to the validation script;
• you have added unit tests for any new or improved feature;
• you have checked pdi/docs/CheckList.md
• you have checked your code format:
  • you have checked that you respect all conventions specified in CONTRIBUTING.md;
  • you have checked that the indentation and formating conforms to the docs/formating.astyle;
  • you have documented with doxygen any new or changed function / class;
• you have correctly updated the copyright headers:
  • your institution is in the copyright header of every file you (substantially) modified;
  • you have checked that the end-year of the copyright there is the current one;
• you have updated the AUTHORS file:
  • you have added yourself to the AUTHORS file;
  • if this is a new contribution, you have added it to the AUTHORS file;
• you have added everything to the user documentation:
  • any new CMake configuration option;
  • any change in the yaml config;
  • any change to the public or plugin API;
  • any other new or changed user-facing feature;
  • any change to the dependencies;
• you have correctly linked your MR to one or more issues:
  • your MR solves an identified issue;
  • your commit contain the Fix #issue keyword to autoclose the issue when merged;
• you have added to this file any other check that was missing.