Check for existing references reports error when reference defined in another file

Currently the validation checks if a bean/endpoint/dataformat reference has a definition in the same camel context file. It doesn't take into account that it must not be defined in the same context. That check should either be removed or the check logic has to be improved to cover all places for those definitions.

For now I would simply disable that check.