More conditions based on source column for consul sql updates

[dangra]

missed some cases in #265

[jeromegn]

This could still cause corrosion consul sync to overwrite a a service it's not supposed to, but it's going to be rare.

For example:

• Corrosion gets a partial row update before the insert for the same primary key (e.g. only gets status = "passing")
• Corrosion store default values for other columns (so: source = NULL) because it doesn't have enough information to build the row
• Somehow 2 services with the same node, id are handled by Consul and the other source
• These conditions would match even though they shouldn't.

This should be rare and only happen if multiple sources handle the same services...