Upgrade WebdriverIO to v9.20.0

[Yuyuutsu]

What is the context of this PR?

This PR upgrades all WDIO packages to v9.20.0 and updates our functional tests to comply with the new upgrades.

Changes made

• getHTML() no longer takes a boolean flag. It now accepts an options object. The default options:
  ({ includeSelectorTag: true, prettify: true }) were causing differences in the returned HTML, which led to assertion failures (formatting changes and missing alt attributes on logo tags). We have to explicitly set these values to false.

• newWindow() now needs to explicitly have a URL value. In v8, newWindow() implicitly opened about:blank when no URL was provided. In v9 this implicit default was removed, so we now explicitly pass 'about:blank' when opening a new window.

• SDS Tests in GA are failing when in the main test, but work when separated into their own job with "MAX_INSTANCE=1". Also the very first SDS launch always hits the “Sorry, there is a problem with this service” page. So a new helper function - openQuestionnaireWithRetry(). I think we need an investigation on why SDS is failing like this in GA only.

• Chrome options also updated in an attempt to make tests more consistent.

• Babel dependencies have also been upgraded to latest versions

How to review

• Run Functional tests locally and see if they all work as expected
• Check all test-functional commands work as expected
• Do you agree with the changes made? There are multiple routes we can take with these changes, happy to hear out any suggestions.

Links

• https://webdriver.io/blog/2024/08/15/webdriverio-v9-release/
• https://webdriver.io/docs/api/element/getHTML/
• https://webdriver.io/docs/api/browser/newWindow/

Checklist

• New static content marked up for translation
• Newly defined schema content included in eq-translations repo

[berroar]

Was just wondering with:
Some tests became flaky due to reliance onbrowser.pause() to avoid race conditions. Therefore a new helper function has been added, waitForPageToLoad(), which waits for the page to fully load.
Did we test without replacing these at all? I think they were initially added before we went back to running consecutively?

[Yuyuutsu]

Was just wondering with: Some tests became flaky due to reliance onbrowser.pause() to avoid race conditions. Therefore a new helper function has been added, waitForPageToLoad(), which waits for the page to fully load. Did we test without replacing these at all? I think they were initially added before we went back to running consecutively?

Tested on a seperate branch and works without browser.pause. Changes have now been added to this branch 👍

[berroar]

Observing a lot of The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D` in the run logs.

[Yuyuutsu]

Observing a lot of The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D` in the run logs.

Transitive package from:

@babel/[email protected]
└─ @babel/[email protected]
   └─ [email protected]
      └─ [email protected]

I have upgraded the dependencies in babel so now baseline-brwoser-mapping is on the latest version.
Other devs are having the same issue with this warning message:
web-platform-dx/baseline-browser-mapping#107