Fix the port used by ChromeDriver after it started to use a random port since the last upgrade

We already had this problem on the development VM which is why it is documented in https://gitlab.opencode.de/umwelt-info/metadaten/-/blob/main/harvester/src/browser.rs, but the last upgrade of the Chromium snap brought it to the staging VM as well.