Don't allow parent Node mappings to be the same/or one of the node UUID mapping

[DiegoPino]

what?

There is ways people can break their ingest by selecting for the parent Node columns the same used for uuid column mapping. Validate that both are mutually exclusive before allow people to continue

Also @alliomeria (buuuuh) found a bug where if you select manually a UUID mapping and process. And then come back for another set, check auto uuid and process the system will hide the previous mapping but still use it. Making all bleed and meh...

This was just fixed and will go into #107 too. But this also showed that if auto uuid is disabled we are still trying to be smart and (bad) generating anyways UUIDs. This might be great, but is inconsistent with the expected behavior. Better not override columns even if the values are wrong, simply not process them if that is the case? (question for @alliomeria and @karomabiles)