[Bug Report] Aliases not changed on performer scrape before alias uniqueness is tested

[Darklyter]

When scraping a performer that already exists in the Stash database, if they have an alias that matches the performer name in the existing alias list then you will get an error message on that alias line after scraping from StashDB even though the alias now doesn't match.

For example, in testing I had "Dillan Lauren", who has an existing alias of "Dillan Lauren" in position 1 of the alias list. When I scraped from StashDB, that field then was changed to "Brit" but I still had an "alias_list must be unique" error on position 1.

Simply removing "Brit" and putting it straight back in (Ctral-A, Ctrl-X, Ctrl-V) clears the error and allows for saving.

It looks as though the alias_list uniqueness check is happening before the StashDB data is applied to the performer, rather than after the alias_list is updated with new information from the database