Introduce the cypress/factory image

[mjhenkes]

Closes #810

This PR introduces a cypress/factory image that can be used to generate a docker container with various combinations of the following.

• node
• yarn
• chrome
• firefox
• edge
• cypress

The factory docker container is also now used to generate cypress/base, cypress/browsers and cypress/included.

See the readme for more details.

On merge to master this should push the new factory image, a new version of included and browsers, but not a new included image (until we update the node version)

[jaffrepaul]

I'd suspect users may want more control over this, so passing in an optional ARG could be useful. This is anecdotal however. We could hold off until the issue arises.

[mjhenkes]

Yeah that was kind of my thought too.

[jaffrepaul]

I didn't have the time to give this a test run myself (esp given the additional, personal setup), but I gave it a good review.
I'm looking at your sample Circle runs, too many args caught my eye and was curious what the implications are.

Otherwise, great stuff @mjhenkes. This is big.

[mjhenkes]

@jaffrepaul

I'm looking at your sample Circle runs, too many args caught my eye and was curious what the implications are.

Nice catch! the check was failing but circle wasn't warning me. Should be fixed now.

[jordanpowell88]

@mjhenkes

I understand that users won't need to do this anymore but there are still use cases where we need to publish new images. I was really referring to those instances. Not a show stopper by any means but just figured it was worth noting this change for historical purposes nonetheless

[Joelasaur]

This is the best feature I've never known I've needed, thank you so much for adding this. Incredibly helpful to the developer experience.