[Bug Report] Adding Performer from Scene Tagger Fails

[bdbenim]

Describe the bug
When scraping a scene from stash-box in the scene tagger view, the user is prompted to add missing performers with their data pre-filled from stash-box. If a performer being added has an alias matching their primary name, adding them to the user's stash instance will fail.

To Reproduce
Steps to reproduce the behavior:

1. Go to the scene tagger view and select a stash-box instance as the source
2. Choose a scene which exists in stash-box and for which not all performers are in the local database (if necessary, delete a performer or their Stash ID for testing)
3. Click on 'Scrape by fragment'
4. For the missing performer, click 'Create' and then 'Save'
5. If the performer has an alias matching their primary name, an error message will be displayed

Expected behavior
The duplicate alias should be ignored and the performer added as normal. Alternatively, details should be editable in the "Create Performer" modal, which would allow the user to manually delete the bad data.

Screenshots

Stash Version: (from Settings -> About):

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 0.24.1

[Maista6969]

Just had a related issue pop up with performers who have duplicate aliases on StashDB

StashDB considers different casings of the same name to be unique aliases, see for example Syren De Mer who has both "Syren DeMer" and "Syren Demer". Should Stash follow this pattern as well, or should we deduplicate these aliases when adding new performers? If so, which one to pick? 😅