Chrome Blocking iocm.js Upon Microsoft OAuth Login Attempt

Within the last week, since updating Chrome (their usual forced version updates), I have began to see intermittent errors when logging in to Microsoft OAuth to access our web application using Single Sign On.  The browser displays this generic "We couldn't sign you in. Please try again." error...

I contacted our network support and requests from MFA are not even being sent for authentication in this case.  The browser console shows this error:

contentscript.js:33 Refused to load the script 'chrome-extension://2bf9ab2c-2940-4c17-bd84-4a098b445e78/common/iocm.js' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

injectJSFile @ contentscript.js:33
injectIocmOnPage @ contentscript.js:156
(anonymous) @ contentscript.js:281
(anonymous) @ contentscript.js:457Understand this errorAI
19Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.

And the network tab clearly shows that this iocm.js file is being blocked from being executed:

When we search my computer, this file is only found in my SmartBear directory, so it appears that this file is part of the SmartBear package and running tests:

Our developers recommended deinstalling the SmartBear browser extension (which of course will result in me not being able to run tests in Chrome).  And they also enabling the "Allow access to file URLs" setting which is within the SmartBear Test Extension settings, based on some research where people were getting similar messages for various browser extensions...

Is anyone else experiencing this issue or has in the past?  It seems to have begun within the last week for me and I can't get a successful run of tests which normally run without issue.