Correct the host used for consul->pgbouncer pgpass

Closes gitlab-org/build/team-tasks#45

See merge request gitlab-org/gitlab-ee!3426

Introduce a new EE::Admin::UsersController module

See merge request gitlab-org/gitlab-ee!3319

Introduce a new EE::Concerns::LfsRequest module

See merge request gitlab-org/gitlab-ee!3322

Tweak consul.configuration.retry_join examples

Closes gitlab-org/build/team-tasks#29

See merge request gitlab-org/gitlab-ee!3422

Introduce a new EE::ServiceParams module

See merge request gitlab-org/gitlab-ee!3321

Introduce a new EE::Admin::GroupsController module

See merge request gitlab-org/gitlab-ee!3320

On failover the consul agent notifies the pgbouncer by running
`gitlab-ctl pgb-notify --newhost ADDRESS --user pgbouncer --hostuser gitlab-consul`.

For the documented configuration, this turns into a connection to the
pgbouncer service on 127.0.0.1, which may not be what was selected for
PGBOUNCER_HOST in the pgpass file, leading to authentication failures.

In user information we introduce a new variable, CONSUL_SERVER_NODES,
to name this existing 'You need to know the addresses of the consul
servers' piece of information.  Then later in the example configuration
files we refer back to that variable.

https://gitlab.com/gitlab-org/build/team-tasks/issues/29

Add warning when Geo is configured insecurely

Closes #3904

See merge request gitlab-org/gitlab-ee!3368

Removed dependent constraint!

Closes #4024

See merge request gitlab-org/gitlab-ee!3377

Geo: Expire and resync attachments from renamed projects in secondary nodes when using legacy storage

See merge request gitlab-org/gitlab-ee!3259

Geo: Expire and resync attachments from renamed projects in secondary nodes when using legacy storage

Simplify docs review script ee

Closes #3931

See merge request gitlab-org/gitlab-ee!3399

PG HA: Rework headings to get unique links

Closes gitlab-org/build/team-tasks#30

See merge request gitlab-org/gitlab-ee!3419

As the flow of the PG HA documentation needs you to keep in mind several
roles, and visit them at multiple steps of the process, we end up with
mutiple headings called `Consul`, `PostgreSQL`, `Database`, and
`Pgbouncer`.

These headings become HTML anchors so a user can link to a particular
section of the document, but when needing to link to the Post-configure
of Consul you'd end up at the Consul section in user information.

Here we reword the headings.  They are less terse, but it allows for
deep-linking.

https://gitlab.com/gitlab-org/build/team-tasks/issues/30

Docs for epics

See merge request gitlab-org/gitlab-ee!3393

Port WikiService.WikiGetAllPages RPC migration to EE

See merge request gitlab-org/gitlab-ee!3408

Resolves error when using a bad formatted URL on "Pull from remote" & "Push to remote" sections

Closes #833

See merge request gitlab-org/gitlab-ee!3389

We need to make room for Runner and Omnibus docs.
This change makes sure the correct values are defined
based on CI_PROJECT_NAME.

Remove the full-scan option from the Geo log cursor

Closes #4050

See merge request gitlab-org/gitlab-ee!3412

- Adds rescue clase to import_url method
- Ensure RemoteMirror model also validates the url

Closes #833

This option was undocumented and is not generally useful, and the code is
difficult to maintain.

Add create epic

Closes #3937 and gitlab-org/build/team-tasks#33

See merge request gitlab-org/gitlab-ee!3293

Make GeoLogCursor Highly Available

Closes #2917

See merge request gitlab-org/gitlab-ee!3305

Add epics to EEU license

Closes #3731

See merge request gitlab-org/gitlab-ee!3387

Fix permissions check for destroy epic-issue link

Closes #4044

See merge request gitlab-org/gitlab-ee!3403

Explain how to generate POSTGRESQL_PASSWORD_HASH

Closes gitlab-org/build/team-tasks#39

See merge request gitlab-org/gitlab-ee!3404

check if the GeoNode table exists before checking its state

Closes #3334

See merge request gitlab-org/gitlab-ee!3298

Move merge service specs to EE module

See merge request gitlab-org/gitlab-ee!3383

POSTGRESQL_PASSWORD_HASH as with other postgresql password hashes, is
generated from md5(password + username).  The previous description
suggested it was just a hash of POSTGRESQL_USER_PASSWORD, which leads to
authentication failures

Closes https://gitlab.com/gitlab-org/build/team-tasks/issues/39

Specify which password should be used on Pgbouncer

Closes gitlab-org/build/team-tasks#37

See merge request gitlab-org/gitlab-ee!3400