Add remote docker chrome target for CI server

[MaciejJaroszewski]

PR resolves:

1. Problem with connect to external docker image with chrome-headless
2. Problem with navigating through different stories via iframes - probably bumping dependencies, additional configuration serve-handler and increasing timeout would help
3. process exits when all test passes - after fix first and second problem, all tests would pass if correct, but proces didn't exit and circle CI waiting for 10 minutes and after that CI server kill process and throw error (circleCI timeout)

Thanks @dbartholomae for initial commits.

Resolve issue #94

[koshov]

@MaciejJaroszewski thank you for pushing this forward!
I tested your fork on one of my projects, but am still getting the Timeout on CircleCI. Have you been able to revisit this? I would be happy to lend a hand if there are any details on what is outstanding to get Loki working on CircleCI.

[codrin-iftimie]

I know I'm late to the party, but would it be easier to use the "chrome.app" as the target in this case?
And have the loki.config.js file select which one should be used as target based on a ENV variable, like CI
Something like:

// loki.config.js

module.exports = {
  configurations: {
    desktop: {
      target: process.env.CI ? "chrome.app" : "chrome.docker",
      width: 1366,
      height: 768,
      deviceScaleFactor: 1,
      mobile: false,
    },
  },
};

[kadosa]

I know this PR is quite old, but I'm wondering if there's a chance to get this looked at again? Or if there's a suggested way of using chrome.docker on CircleCI?