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

Remove the full-scan option from the Geo log cursor

Closes #4050

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

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

It was a little unclear which password we should specify; it turns out
it's the pgbouncer password, which is used by consul to signal to the
pgbouncer service it should reload.

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

Fix docs to label file locking as EEP-only

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

Introduce default usernames earlier

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

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

Update the sample `consul members`

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

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

`CONSUL_USERNAME` and `PGBOUNCER_USERNAME` are used to derive
`CONSUL_PASSWORD_HASH` and `PGBOUNCER_PASSWORD_HASH`, so we should let
the user know their default values so we're not expecting them to jump
forward to the notes on the service.

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

CE Upstream - Monday

Closes gitlab-qa#99, gitaly#681, gitlab-qa#88 et gitlab-ce#31811

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

Upon reaching this step in the documentation we should have added 7
nodes to the consul environment; 3 servers, 4 clients, so update the
output to reflect that.

Additionally 10.1.2 uses the name `gitlab_consul` for its DC, so bring
that into line.

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

Remove approvals when in empty MR widget state

Closes gitlab-ce#39009

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

Ide lock files

Closes #3918

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

this test should be only testing for code that is in the
described_class, not on another job that run afterward.

I also think that the coverage of this task is sufficient with
the CreateForkNetworkMembershipsRange tests.

Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/39009

add related issues component to Epic

Closes #3551

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

* origin/fix-populate-for-networks-range-spec:
  removed the dependency on another background job running inline

[ci skip]

[ci skip]