Since GitHub doesn’t apply these constraints to theirs wiki slug
allowing characters like `,`, `:`, `*`, etc, we need to relax our
constraints or some wiki pages will not be available after they were
imported.

For an example the Devise project have a wiki page with the following
slug: “How To: Add sign_in, sign_out, and sign_up links to your layout
template”

fixes bug with commenting on merge requests



See merge request !2415

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Add browser for build artifacts

Discussion in #3426, closes #3426.

See merge request !2123

Add variables API

References #4264 

See merge request !2264

Added also a `Gitlab::Ci::Build::Artifacts::Metadata::ParserError`
exception class.

[ci skip]

We do not want to allow runners to upload a metadata file. This needs to
be generated by Workhorse only.

In this version we will support only relative paths in artifacts
metadata. Support for absolute paths will be introduced later.

This changes the format of metadata to handle paths, that may contain
whitespace characters, new line characters and non-UTF-8 characters.

Now those paths along with metadata in JSON format are stored as
length-prefixed strings (uint32 prefix).

Metadata file has a custom format:

1.   First string field is metadata version field (string)
2.   Second string field is metadata errors field (JSON strong)
3.   All subsequent fields is pair of path (string) and path metadata
     in JSON format.

Path's metadata contains all fields that where possible to extract from
ZIP archive like date of modification, CRC, compressed size,
uncompressed size and comment.