connection.switch.arp_inspection potential spurious result

**Describe the bug**
Conducted separate 2 tests on the same DUT, from separate Tetsrun machines (not sure whether this makes a difference, as the machine hardware/spec for both machines is identical).

_Test 1_

_Test 2_

For test 2 this was shown in the logs.

However at the same timestamp in connection.pcap, the DUT can clearly be seen announcing that 10.10.10.12 is at 00:60:74:f0:29:90.

Is this a race condition?

Additionally, an ARP packet pertaining to 10.10.10.14 doesn't appear in connection.pcap until 7 minutes later at 15:45:07. How can this be reported/inferred at 15:38:11 in the log file above?

**Expected behavior**
Identical results should occur on identical tests of the same DUT.

**Error logs**
[QSC QIO-L4O v9.13.0-2412.002 (test 1).zip](https://github.com/user-attachments/files/18866243/QSC.QIO-L4O.v9.13.0-2412.002.test.1.zip)
[QSC QIO-L4O v9.13.0-2412.002 (test 2).zip](https://github.com/user-attachments/files/18866246/QSC.QIO-L4O.v9.13.0-2412.002.test.2.zip)

**Environment (please provide the following information about your setup):**
- Version 2.1