Chrome 128 new headless mode causing issues on consecutive scans

[straker]

When Chrome 128 released it introduced a problem with the way we are doing our unit tests. Specifically for our full integration tests dealing with partial runs. What would happen is that after we performed a partial run and then would perform a normal axe run right afterwards, the window height of the page would change and our tests that compare the results would then report not equal (since the height values were different). We believe that Chrome 128 introduces something that changes how the infobar about being controlled by automated tests appears, and that causes problems in our tests.

To fix the problem we ignored the height in the comparison, but the height changing could cause other problems that we may not know about yet. We found that another workaround was to add --disable-infobars to the chrome arguments on startup. We might need to create docs around this behavior.