fix(browserstack-service): declare webdriverio as a dependency, not a peer

The extraction moved webdriverio from dependencies (as in the WebdriverIO monorepo /
the published @wdio/browserstack-service@9.29.1) into peerDependencies (^9.0.0). That
forces the consumer's webdriverio to ^9 and npm ERESOLVEs against any dep peering
webdriverio@^7||^8 (e.g. wdio-chromedriver-service@^8) — an install failure the
monorepo package never had. Move it back to dependencies to restore install parity.

Verified: official npm 9.29.1 and monorepo source both keep webdriverio in
dependencies and peer only @wdio/cli; the standalone was the sole divergence.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: AakashHotchandani

.changeset/fix-webdriverio-peer-to-dep.md

@@ -0,0 +1,5 @@
+---
+"@wdio/browserstack-service": patch
+---
+
+Declare `webdriverio` as a dependency instead of a peerDependency, matching the package published from the WebdriverIO monorepo. The extraction had moved `webdriverio` into `peerDependencies` (`^9.0.0`); npm then forced the consumer's `webdriverio` to `^9`, which conflicts with any project that also depends on a package peering `webdriverio@"^7 || ^8"` (e.g. `wdio-chromedriver-service@^8`) and surfaced as an `npm ERESOLVE` on install — a failure the monorepo-published package never had. Restores install parity with the upstream package; no user-facing API change.

package-lock.json

@@ -72,11 +72,11 @@
     "yauzl": "^3.4.0",
     "@wdio/logger": "^9.0.0",
     "@wdio/reporter": "^9.0.0",
-    "@wdio/types": "^9.0.0"
+    "@wdio/types": "^9.0.0",
+    "webdriverio": "^9.0.0"
   },
   "peerDependencies": {
-    "@wdio/cli": "^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^9.0.0",
-    "webdriverio": "^9.0.0"
+    "@wdio/cli": "^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^9.0.0"
   },
   "devDependencies": {
     "@bufbuild/buf": "^1.55.1",