Object type mapping case matching incorrectly displayed for "Case Insensitive" option

Issue Summary

When customer create/update an import object type mapping, the "Identifier case matching" option will always display "Case sensitive" even if they chose "Case Insensitive"

Steps to Reproduce

1. Create an import configuration
2. Create or edit an existing object type mapping and selecting "Case Insensitive" for "Identifier case matching"
3. Go back and edit the object type mapping of the mapping at step 2

Expected Results

Case Insensitive should be displayed in the edit dialog

Actual Results

Case Sensitive is displayed in the edit dialog

Workaround

The case insensitive selection is actually saved in the backend and returned to the frontend correctly, but the frontend is not displaying the result correctly.

Currently there's no workaround to have the option displaying properly.