vibration_browsertest.cc tests vibration integration between Blink and the browser, e.g.:
- Checking that executing navigator.vibrate() in JS causes a host-side vibration request
- Checking that an outstanding vibration is cancelled if the main frame is reloaded

It does this by injecting a fake VibrationManager impl into RenderFrameHost's InterfaceRegistry. However, there is no easy mechanism to support that once VibrationManager is hosted in the Device Service. Thus, we first need to eliminate this mechanism. Possible approaches:

- Expose a test-only interface on VibrationManager wherein it can receive a VibrationManager to which it will forward all requests. Access to this interface could be guarded by manifest specification such that it is only accessible from //content/browser.

- Expose the ability to inject a fake service impl. Perhaps this could just be done at the //content level?

- Replace these browsertests entirely with layout tests. The browsertests are not testing the real impl in any case. Would need to map the actions being tested (e.g., reloading main frame) to flows to take in layout tests.