UP Deduplication Design Documentation (#17143)

* Porting draft of Deduplication doc from sharepoint

* Fixing up formatting

* Sharepoint feedback pt 1

* Additional sharepoint feedback, restructuring to focus on design instead of requirements

* Final sharepoint feedback changes, consolidation of information, formatting

* More polish

* More polish, adding in Submission History examples

* Small updates

* Smaller feedback changes

* UP SRD proprosal

* Updating sender setting info

* UP SRD Convert step updates

* Updating SRD for allowDuplicate http param

* updates for initial db invest and key field class mock

* light format/wording changes

* Adding azure events

* Feedback and db investigation updates

* More details on logging and azure events

prime-router/docs/design/design/data-model.md

@@ -184,7 +184,7 @@ Organizations serve as containers for Senders and Receivers, but have their own
 
 #### Sender Settings
 
-Sender settings allow the Sender to indicate what [topic](./topic.md) they would like to use as well as the format of their message. `allowDuplicates` allows Senders to indicate if duplicate Items in a Report should be filtered out prior to processing. For more information regarding `allowDuplicates`, see documentation on the [Receive step](../../universal-pipeline/receive.md) of the Universal Pipeline.
+Sender settings allow the Sender to indicate what [topic](./topic.md) they would like to use as well as the format of their message. `allowDuplicates` allows Senders to indicate if duplicate Items in a Report should be filtered out prior to processing. For more information regarding deduplication, see [Universal Pipeline Deduplication](../design/deduplication/deduplication.md).
 
 Example Sender settings configuration. Deprecated options have been omitted.
 ```json