Support alternative mapping relationships in concept approval workflow

[michaelbontyes]

Currently, all concept mappings are assumed to be of type SAME-AS when approved to the target repository. Based on feedback (Andy, March 24), this assumption does not apply to all use cases.

While SAME-AS should remain the default relationship type, users must have the ability to explicitly flag mappings as NARROWER-THAN, BROADER-THAN, or APPROXIMATE, depending on the context.

---

Acceptance Criteria:

1. Default Relationship Type:

   • Approved mappings default to SAME-AS unless otherwise specified by the user.

2. Alternative Relationship Options:

   • The following mapping types must be available in the UI for selection:
     • SAME-AS (default)
     • NARROWER-THAN
     • BROADER-THAN
     • APPROXIMATE

3. UI Behavior:

   • During mapping review or approval, users should be able to:
     • View the default mapping relationship.
     • Select a different relationship type from a dropdown or toggle before finalizing approval.

4. Validation & Storage:

   • The selected relationship type is stored correctly.
   • The relationship type should be reflected in any exports.

5. QA Scenarios:

   • Approve a mapping with default SAME-AS: confirm it's stored as such.
   • Change the mapping to NARROWER-THAN or other types before approval: confirm the change is saved.
   • Ensure mapping relationships are persisted and retrievable correctly.