Same corrlator nonce misbehaviour

[d-linko]

If there are multiple entries with the same correlator_nonce and agent_id in the execution_set table the report display in route will run into errors probably because core is using a one_or_none select.
The database should be rejecting the new entry with duplicative correlator_nonce but looks like is occurring after the whole system is restarted

[BrianSipos]

It is a normal and expected situation that an agent sends multiple RPTSET with the same nonce value. So the ANMS will need to handle this cleanly.