Apparently this workaround is no longer necessary. I think Google fixed this issue in Chrome 111, since all my systems now again accept the plugin...
