Add Missing Fields to Potential Match Response Candidate Attributes

[benno]

The Potential Match Response JSON Schema definition does not include the SOR field, even though there are examples using it.

An optional matchRequest field should also be added to indicate the associated Match Request ID.

Both fields are already supported by COmanage Match.

Consider adding an explicit sorid field (since it's part of the request URL), even though it can be encoded as an Identifier in the attribute set.