Extend Link Instances with MWL Entry service to enable application of link strategy specified by client

[vrindanayak]

Extend Link Instances with MWL Entry service to include query parameter strategy with values either as MERGE or IOCM to indicate applicable linking strategy required by the client.

On not specifying the query parameter, the default behavior of service prevails.

On using strategy query parameter :

Value	Meaning	Notes
MERGE	Always merge MWL's attributes into the linked study / series attributes	Same to default behavior's Study IUID of study to be linked matches with that of MWL
IOCM	Emulate IHE transactions Rejection Note Stored - RAD-66 / Replacement Instances Stored - RAD-74	Same to default behavior's Study IUID of study to be linked does not match with that of MWL

On not using strategy query parameter, default behavior applies :

Condition	Meaning	MWL's Attributes reflected in Study
Study IUID of study to be linked matches with that of MWL	Merge MWL's attributes into the linked study / series attributes	All of MWL attributes are considered. Additionally, as the MWL / Study - Series IODs are slightly different in terms of attributes' naming - StudyDescription <-> RequestedProcedureDescription - StudyID <-> RequestedProcedureID - RequestAttributesSequence <-> ScheduledProcedureStepSequence Requires #4016
Study IUID of study to be linked does not match with that of MWL	Emulate IHE transactions Rejection Note Stored - RAD-66 / Replacement Instances Stored - RAD-74	All of MWL attributes + Patient (of MWL) attributes are considered. Additionally, as the MWL / Study - Series IODs are slightly different in terms of attributes' naming - StudyDescription <-> RequestedProcedureDescription - StudyID <-> RequestedProcedureID - RequestAttributesSequence <-> ScheduledProcedureStepSequence