Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created in Jira under that version, the integration randomly selects one of the linked releases as the parent and creates the feature in that workspace.

Random selection is not an ideal scenario. Instead, the integration should recognize that it cannot logically determine the intended destination for the new child record and include it as an import candidate with the matching parent integrations as options from which to choose. The user can then select the appropriate Aha! integration/workspace to use to import the record.