Due to a misbehavior in artifactory, the wrong http status code is returned and the build will stop immediately. This happens if you access a virtual repository which contains a repository which requires authentication.

As a workaround a virtual repository is used, which does not include non-public repositories.

https://www.jfrog.com/jira/browse/RTFACT-13797

- Orchestrator upgrade was required as by default it was setting these properties

- add should minimum match eq 1 to user index queries
ES 7.X changed behaviour in case filter query with bool it defaults to '0'
https://www.elastic.co/guide/en/elasticsearch/reference/7.x/breaking-changes-7.0.html#_the_filter_context_has_been_removed

- fix issue index routing param
ES 7.X helped discover this bug as new setting has been auto configured which is 'index.number_of_routing_shards'.
This has changed how documents are distributed across shards depending on how many shards the index has.

Without that change issues docs has been incorrectly routed to the same shard hash as projects and it worked no matter what routing key you used projectUuid or auth_projectUuid.

- update ngram and edge_ngram names to match with es 7.x
nGram and edgeNgram has been deprecated in favour of ngram and edge_ngram
https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#deprecated-ngram-edgengram-token-filter-cannot-be-used

- remove `_all : enabled` usage from UT
This field was already deprecated in 6.X, now it has been removed.
https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#all-meta-field-removed

- add Elasticsearch High Level REST client dependency

- use sonar.search.port for ES HTTP

- main process use ES Rest client to check ES status

- sonar.cluster.search.hosts has HTTP ports on APP nodes
also sonar.search.port and sonar.search.host MUST be configured on each Search node with the host and HTTP port of the current node

- use Elasticsearch high level rest client

- use in EsTester

- use as primary es client

- use indices api to get all indices name instead of cluster api

- use cluster health api to check cluster state

- support raw requests for 'nodes/_stats' and '_cluster/stats'

- support raw requests for 'indices/_stats'

- leave netty4plugin as testCompile dependency it is used in UTs

- all ES non-test calls go through EsClient class

- add rest client ES profiling

This reverts commit 6d13dd2f

* SONAR-13913 Remove usage of Orchestrator#resetData

* Remove ProjectAnalysisRule

* Upgrade to Orchestrator 3.31

* SONAR-13913 Remove BackendCleanup class

* Remove code related to no more existing tables

SONAR-13833
SONAR-13907
SONAR-13909
SONAR-13910
Upgrade analyzers

to mitigate the vulnerabilities brought by the bundled
jackson-core dependency.

The release notes of 3.12.8 and 3.12.9 highlights only bug-fixes:
https://docs.hazelcast.org/docs/rn/index.html#3-12-9

The main reason is to fix potential vulnerabilities:

- CVE-2020-13934 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13934
- CVE-2020-13935 https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13935

Release notes: http://tomcat.apache.org/tomcat-8.5-doc/changelog.html

* SONAR-13576 Remove sonar-typescript-plugin

* Update sonar-javascript-plugin to 6.3.0.12464

Bug-fixes listed in https://docs.hazelcast.org/docs/rn/index.html#3-12-7

Fixes potential vulnerability CVE-2020-13692

The vulnerability https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9484
is not exploitable but it generates a false-positive in SCA reports.
Upgrading kills the noise.

Avoids vulnerability https://issues.apache.org/jira/browse/IO-556