L3Out Subnet (F0467: prefix-entry-already-in-use) should remove dup entries and show all other conflicting objects

[takishida]

(use upvote 👍 for attentions)
Describe the enhancement
When the L3Out is deployed on multiple leaf nodes, fault F0467 is raised for each node. This results in the duplicated entries (one for each node) in the script output. The dup entries should be removed.

Also, this check is simply showing the information in the fault which only includes one L3Out out of two causing the conflict. This should be enhanced to scan other L3Outs to show both L3Outs so that users don't need to struggle to find the other half.

Current behavior/output

[Check 23/67] L3Out Subnets (F0467 prefix-entry-already-in-use)...                                                 FAIL - OUTAGE WARNING!!
  Fault  Failed L3Out EPG               VRF VNID  VRF Name  Prefix already in use  Recommended Action
  -----  ----------------               --------  --------  ---------------------  ------------------
  F0467  uni/tn-TK/out-OSPF/instP-EPG1  2719744   VRFA      10.0.0.0/8             Resolve the conflict by removing the faulted configuration for the overlapping prefix
  F0467  uni/tn-TK/out-OSPF/instP-EPG1  2719744   VRFA      10.0.0.0/8             Resolve the conflict by removing the faulted configuration for the overlapping prefix

Below is the query used by this check. One fault for each node (103 and 104) for the same subnet. This resulted in two duplicated entries in the output above.

admin@apic1:techsupport> icurl -s 'http://localhost:7777/api/class/faultInst.json?query-target-filter=and(wcard(faultInst.changeSet,"prefix-entry-already-in-use"),wcard(faultInst.dn,"uni/epp/rtd"))' | python -m json.tool | grep dn
                    "dn": "topology/pod-2/node-103/local/svc-policyelem-id-0/uni/epp/rtd-[uni/tn-TK/out-OSPF/instP-EPG1]/nwissues/fault-F0467",
                    "dn": "topology/pod-2/node-104/local/svc-policyelem-id-0/uni/epp/rtd-[uni/tn-TK/out-OSPF/instP-EPG1]/nwissues/fault-F0467",

Suggested behavior/output

[Check 23/67] L3Out Subnets (F0467 prefix-entry-already-in-use)...                                                 FAIL - OUTAGE WARNING!!
  Fault  Failed L3Out EPG               VRF VNID  VRF Name  Prefix already in use  Recommended Action
  -----  ----------------               --------  --------  ---------------------  ------------------
  F0467  uni/tn-TK/out-OSPF/instP-EPG1  2719744   VRFA      10.0.0.0/8             Resolve the conflict by removing the faulted configuration for the overlapping prefix
  F0467  uni/tn-TK/out-BGP/instP-EPG1   2719744   VRFA      10.0.0.0/8             Resolve the conflict by removing the faulted configuration for the overlapping prefix

The second line is now the other half of the conflicts instead of the dup entries due to the multiple nodes.

To Reproduce
Steps to reproduce the behavior such as:

1. Configure multiple L3Outs with the same subnet (with scope "External Subnet for the External EPG") in their external EPGs
2. Deploy those L3Outs on multiple leaf nodes

Additional context
None