[Bug Report] Tagger used with multiple StashBoxes will lose Performer StashIDs

[scruffynerf]

If you use Performer Tagger, and scrape a performer, and the matched performer already exists with other StashIDs from other stashboxes, hitting the save will cause the loss of the other existing StashIDs, and only the new one is saved.

To Reproduce
Scrape a Performer using StashBox B, and if the Performer already has a StashID from Stashbox A...
It will match, and allow you to save the new StashID.
It then loses any existing StashIDs, and only keeps the new one.

Expected behavior
It should keep any existing stashids as well as add the new one.

Stash Version: (from Settings -> About):
Existed for a while, including up to v.23.1

Confirmed by multiple people.

Corrected by me, as I misunderstood the latest report.
I know @DingDongSoLong4 fixed the scene tagger issues in #4092
and pointed to this other similar issue as long standing (https://discord.com/channels/559159668438728723/559159910550732809/1152724118299496570)

[DingDongSoLong4]

This also happens in the Performer Tagger (not the bulk performer tagger), when updating an existing performer.

A relevant bit of code:

stash/ui/v2.5/src/components/Tagger/PerformerModal.tsx

Lines 171 to 176 in 0b7dcbe

	performerData.stash_ids = [
	{
	endpoint,
	stash_id: remoteSiteID,
	},
	];