[Bug] Harvest Deletes Every Berry Consumed in Memory after That Berry is Harvested

[Snailman11]

Describe the bug

If Harvest would produce a Berry Harvested in a Battle where multiple Berries were Harvested, any Berry that was consumed after it and was moved to the User's Berry memory is lost.
-Berries do not need to all be consumed in the same turn.

Example: (From order of Liechi, Ganlon, Petaya, Apicot, Salac)
(After triggering all of them at once)

• Apicot is Harvested, so as Salac was consumed later, it is cleared from memory
• Ganlon is Harvested, so as Petaya, Apicot, and Salac were consumed later, they are cleared from memory
• Liechi is Harvested, so as Ganlon, Petaya, Apicot, and Salac were consumed later, they are cleared from memory.

Link to Discord's Bug Report (Harvest Doesn't Return Berries?)
https://discord.com/channels/1125469663833370665/1295252012690051105

Reproduction

Use Harvest after consuming multiple Berries in one turn, such as by being knocked to low health, or by Nuzzle with Enigma and Lum Berries. Notice that if the first Berry that was consumed was harvested, new berries are no longer harvested.

	STARTING_WAVE_OVERRIDE: 11,
	STARTING_BIOME_OVERRIDE: Biome.PLAINS,

	MOVESET_OVERRIDE: [Moves.SPLASH, Moves.DISABLE, Moves.RECOVER],
	ABILITY_OVERRIDE: Abilities.HARVEST,

	OPP_LEVEL_OVERRIDE: 40,

	OPP_MOVESET_OVERRIDE: [Moves.SUNNY_DAY, Moves.FALSE_SWIPE],

	STARTING_HELD_ITEMS_OVERRIDE: [
	{name: "BERRY", type: BerryType.LIECHI, count: 1},
	{name: "BERRY", type: BerryType.GANLON, count: 1},
	{name: "BERRY", type: BerryType.PETAYA, count: 1},
	{name: "BERRY", type: BerryType.APICOT, count: 1},
	{name: "BERRY", type: BerryType.SALAC, count: 1}
	
	]

Expected behavior

Harvest should not clear the User's Berry consumption memory when the first Berry is harvested.

Screenshots / Videos

Berry.Queue.Cleared.if.first.is.harvested.mp4

Berry Memory is kept when the first berry is not harvested before the second

hARVESTBERRYQUEUE.mp4

Session export file

No response

User data export file

No response

Additional context

No response