Ensure that browserslist cannot break CI no more

We had a failure a of static-analysis jobs a little over a year ago: #194788 (closed) because browserslist prints warnings in CI in case the caniuse-lite database becomes outdated: https://github.com/browserslist/browserslist/blob/a287ec6/node.js#L367-L384

They recently changed their warning message leading to new errors in CI, which needed to be fixed and backported: !66942 (merged)

The way we fix it currently is by setting the BROWSERSLIST_IGNORE_OLD_DATA variable in CI, which isn't ideal, because the jobs still might fail locally, if you run scripts/static_analysis directly. I think we can circumvent this issue a little better by:

1. Update caniuse-lite monthly (e.g. with https://gitlab.com/gitlab-org/frontend/renovate-gitlab-bot/), this will have no drawbacks. As caniuse complains after 6 months, we would be safe, as our backports are the last three releases
2. We can set BROWSERSLIST_IGNORE_OLD_DATA globally in our docker images.