Allowing lighthouse plugin to connect to remote chrome instances, not only local

[manueljishi]

User story

As stated in this comment (as an example) gitlab allows users to define services. Containers that will be deployed next to the ones running the CI steps and available via network. In this case I'd like to be able to configure a remote chrome instance and configure the lighthouse plugin to connect to the RDP port on said instance instead of running chrome locally. This way I can avoid having to install or maintain the chrome installed in my docker images.

Acceptance criteria

• [ ] Being able to configure hostname flag in lighthouse
• [ ] Being able to configure port flag in lighthouse
• [ ] Allowing my analysis to run without installing any kind of chrome locally to make for lighter and faster jobs

Implementation details

I think to allow the flags we would need to start by implementing the feature in such a way that this function allows the hostname and port flags (and then passes that down to the runner itself) As per bypassing the local chrome install I'd really have to look into that before coming to any conclusions. Maybe when detecting the CHROME_PATH we could check that if it's undefined we have at least a hostname flag to try to connect