[BUG] EDMC does not automatically add finished scan to notyetsolddata.json

[Balvald]

Describe the bug
When scanning the second plant on the same planet EDMC works as intended with the exception to not adding the entry to the notyetsolddata.json.
This then shows in the "Scans in this system" section of the plugin where the recently finished scan does not show up.
(not sure if same planet is relevant, Not sure if a third scan would work again)

Specifically the code that it should run but does not for some reason is:

            if currententrytowrite not in plugin.notyetsolddata[cmdr]:
                # If there is no second Sample scantype event
                # we have to save the data here.
                plugin.notyetsolddata[cmdr].append(currententrytowrite)
                file = plugin.AST_DIR + "\\notsoldbiodata.json"
                with open(file, "r+", encoding="utf8") as f:
                    notsolddata = json.load(f)
                    if cmdr not in notsolddata.keys():
                        notsolddata[cmdr] = []
                    notsolddata[cmdr].append(currententrytowrite)
                    f.seek(0)
                    json.dump(notsolddata, f, indent=4)
                    f.truncate()
                currententrytowrite = {}

located at line 83 within bioscan_event() in eventhandling.py

To Reproduce
Steps to reproduce the behavior:

1. Start EDMC with plugin
2. Do the first full scan of any Exobiology on a planet.
3. Do a second full scan of any Exobiology on that same planet.
4. See error

Expected behavior
the plugin should add the entry of the exobiology scan immediately to the notyetsolddata.json and diplay the finished but unsold scan below the "Scans in this system" line.

Screenshots

Compare what the line "Last Exobiology Scan" says with both the current system and body and see that an entry is missing below the "Scans in this system" line.

Desktop (please complete the following information):

• OS: Windows 11
• AST Version: dev 0.2.7
• EDMC Version: 5.8.1+d81c93c

Additional Context
I can remedy this locally by using the journal crawling function in the settings though it is not great to wait up to a minute after every second scan

[Balvald]

Problem was I did not shallow copy the object into the set that I was testing against so it always was the same in the set of unsolddata and the most current entry.