Code Inspection window can get stuck in refresh/reparsing state

[BZngr]

Rubberduck version information
Version 2.5.2.x (debug)
OS: Microsoft Windows NT 10.0.19042.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.14527.20276
Host Executable: EXCEL.EXE

Description
When both the Test Explorer and Code Inspection windows are displayed, running unit tests (one or more) causes the Code Inspection window to enter a constant state of refresh (spinning ducks).

To Reproduce

1. Open Code Inspections window
2. Open Test Explorer
3. Run a single test or a group of tests.
4. Code Inspections window presents constantly spinning ducks after the first test.

Expected behavior

Code inspection window refresh completes and is available after running unit tests.

Work Around

1. Close Code Inspections window (Test Explorer can remain open or be closed)
2. Manually initiate a Parse using the 'Ready' button.
3. Open Code Inspections window after Parsing is complete...all is well.

Related #5659

[Vogel612]

Running tests should not affect the code inspections window in any way, so that interaction is somewhat worrying...