When we removed charts from the main bundle, we forgot to add them to
the documentation again, so that props etc are properly rendered.

docs: Fix documentation for charts

See merge request !169

feat: Add form radio component

See merge request !152

Apparently when the browser doesn't start we can get cached in a state
where jest doesn't error. By providing this option `--detectOpenHandles`
we can safely detect such probblems and error earlier.

In order to be able to tell puppeteer where the Chromium executable is,
we need to update it

This adds a pre-build stage to our CI which builds a puppeteer docker
image if necessary. The process works like this:

1. Check if the puppeteer version in .gitlab-ci.yml and yarn.lock match,
   if not -> bail
2. Check if we already have an image for that puppeteer version, if yes,
   we do not need to build and can exit
2. Get the chrome revision from the supplied puppeteer version
3. Build a image based on gitlab-build-images:gitlab-puppeteer and
   install the supplied puppeteer version globally
4. Set PUPPETEER_EXECUTABLE_PATH to the path of the chromium revision
   installed globally by puppeteer
5. Check if the executable exists
6. Set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD to true, so that subsequent
   local installs do not try to download the chromium executable
7. Push the image to the gitlab-ui registry

The build stage does not produce any artifact needed for the test stage.
So we can literally just move the build job to the test stage in order
to parallelize efforts.

The update_snapshots job is moved to the pre-build stage as it is a
manual job anyway.

All jobs that do not depend on the results of the build job now have
this dependency removed.

pre-build docker image which contains puppeteer's chromium

Closes #159

See merge request gitlab-org/gitlab-ui!155

## [2.0.3](gitlab-org/gitlab-ui@v2.0.2...v2.0.3) (2019-02-08)

### Bug Fixes

* Updating the version bump ([5b55d726](gitlab-org/gitlab-ui@5b55d726))