Document Data Mapper CSV support requires editing step

From Zoran's comment in the related ENTESB Jira:

Check to see if there are other UI updates that impact the doc as a result of
"With PR#9902 we are upgrading to AtlasMap 2.3.13 which brings in the changes to the Parameters dialog discussed here and on the upstream issue mentioned here. With that the issues with persisting and passing the correct data shape parameters (used only for CSV currently) should be resolved."

In addition to that a new warning has been added to the mapping step, similar to the warning we already had for the data shape mismatch – the one encouraging users to add a mapping step, this one encouraging users to edit the mapping step. This warning covers four cases:

one of the source steps has changed it's output
the target step's input is not compatible with the mapper's output
one of the source steps has gone missing
the target step has gone missing

For any documentation changes. Perhaps in the section 4.3 step 7 here in addition to suggesting to add a mapping step we could also suggest to edit the mapping step (if the warning is on the mapping step that is); and here in the section 7.2