Elasticsearch v6 - migrate from parent/child relationships to joins

What does this MR do?

Since ES6 only allows one mapping type per index and we need to have documents in a single index in order to use join datatypes, I had to make quite a few changes to how we deal with elasticsearch in the codebase:

• I changed all our document types to be doc
• In order to still be able to query per type, I implemented a custom type field in our elasticsearch documents, called simply type
• The join type was created granularly, that is to say, it has a mapping per type: project->issue, project->blob, etc.
• We now use an es_id for elasticsearch's _id field. This is comprised of the model class name and the ID in the database
• Because of the es_id change a lot of changes were required to the elasticsearch-model gem. These changes have been encapsulated in the ee/lib/gem_extensions folder and are injected inside the elasticsearch client initializer.

Breaking changes

We can no longer support Elasticsearch versions under 5.6. This is because the join field is only supported from versions 5.6 and upwards.

Wiki searches now must use a new type: wiki_blob. I've edited existing usages in the codebase but this is good to keep in mind

What are the relevant issue numbers?

#4218 (closed)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• Tests added for this feature/bug
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• EE specific content should be in the top level /ee folder
• For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?

Closes #4218 (closed)

doc/development/elasticsearch.md

@@ -9,19 +9,19 @@ Information on how to enable ElasticSearch and perform the initial indexing is k
 It is recommended to use the Docker image. After installing docker you can immediately spin up an instance with
 
 ```
-docker run --name elastic55 -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:5.5.3
+docker run --name elastic56 -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:5.6.12
 ```
 
-and use `docker stop elastic55` and `docker start elastic55` to stop/start it.
+and use `docker stop elastic56` and `docker start elastic56` to stop/start it.
 
 ### Installing on the host
 
-We currently only support Elasticsearch [up to 5.5](https://docs.gitlab.com/ee/integration/elasticsearch.html#requirements), but `brew` only has elasticsearch 6, 5.6, and 2.4 available. While 2.4 would work you probably want to test things out in the latest one we support.
+We currently only support Elasticsearch [5.6 to 6.x](https://docs.gitlab.com/ee/integration/elasticsearch.html#requirements)
 
-In order to install 5.5.2, you would usually have to hunt down an old homebrew-core commit that contains the recipe for it. We've already done the work for you. Simply run:
+Version 5.6 is available on homebrew and is the recommended version to use in order to test compatibility.
 
 ```
-brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/f1a767645f61112762f05e68a610d89b161faa99/Formula/elasticsearch.rb
+brew install elasticsearch@5.6
 ```
 
 There is no need to install any plugins