The one click update feature updates the code, then on the next page view the db upgrade screen is shown. The actions in between these two components use new code, but an old database schema. This PR makes sure we ignore unknown column errors in the bruteforce detection feature if we're in the one click update process.
@flamisz just fyi, so you're aware if you have to touch this code: this is for the oneclickupdate feature which is extremely hard to test locally. The feature downloads a package from builds.matomo.org, unzips it and replaces the current version of matomo with it. To test it locally w/o a build on builds.matomo.org you'd have to use the matomo-package repo to build a package from 4.x-dev code, then create a new release channel to get it from localhost, then initiate the process. Personally, I find using the test on travis to be a lot less trouble.