update README

Author: silesky

packages/consent/consent-tools-integration-tests/README.md

@@ -1,8 +1,4 @@
-Why is this using wd.io instead of playwright?
-
-- Webdriver.io is committed to the Webdriver Protocol, which is a community-driven spec (as opposed to Chrome Webdriver Protocol.). Playwright uses the Chrome Webdriver protocol for chrome and it's own [custom protocol](https://github.com/microsoft/playwright/issues/4862) for safari / edge.
-- Webdriver.io protocol allows for much better device support-- such as ie11.
-- Webdriver.io has native support for lighthouse and lots of other cool stuff!
+# @internal/consent-tools-integration-tests"
 
 ## Project structure
 - `/public` - Test server root
@@ -18,12 +14,3 @@ Why is this using wd.io instead of playwright?
 ```
 yarn . test:int
 ```
-
-### Debugging Tips:
-- Webdriver.io has the handy `browser.debug()` command.
-
-- You can serve the static pages by themselves (without Playwright) with the following:
-```
-yarn webpack -w &
-npx live-server .
-```