Upgrade Gerrit to 3.4

The actually upgrade will be performed manually, but this change will be
used to update the docker-compose.yaml file.

If we land this change prior to the upgrade then note the
manage-projects commands will be updated to use the 3.4 image possibly
while gerrit 3.3 is still running. I don't expect this to be a problem
as manage-projects operates via network protocols.

Change-Id: I5775f4518ec48ac984b70820ebd2e645213e702a

playbooks/roles/gerrit/defaults/main.yaml

@@ -6,7 +6,7 @@ gerrit_run_compose_up: false
 gerrit_run_init: false
 gerrit_run_init_dev_mode: false
 gerrit_packed_git_open_files: 4096
-gerrit_container_image: docker.io/opendevorg/gerrit:3.3
+gerrit_container_image: docker.io/opendevorg/gerrit:3.4
 gerrit_container_volumes:
   - /home/gerrit2/.launchpadlib:/var/gerrit/.launchpadlib
   - /home/gerrit2/.ssh:/var/gerrit/.ssh

playbooks/zuul/templates/host_vars/review99.opendev.org.yaml.j2

@@ -97,7 +97,7 @@ gerrit_run_init_dev_mode: true
 gerrit_storyboard_token: 52514e74-4b8f-4d6d-a29a-a6262f97578a
 gerrit_email_private_key: wjpkxebohgbid6rpuwpfrYsouxpgseluqir6yupppBczoezj
 gerrit_rest_token_private_key: A83fAC8x72wxcu
-gerrit_container_image: "docker.io/opendevorg/gerrit:{{ zuul_test_gerrit_version | default('3.3') }}"
+gerrit_container_image: "docker.io/opendevorg/gerrit:{{ zuul_test_gerrit_version | default('3.4') }}"
 gerrit_under_test: true
 gerrit_launchpad_auth:
   access_token: 'token'