webapp: fix keycloak setup

The current production/staging is broken. My bad, i missed that this morning on !212 (closed).

I fixed it manually right now and restarted the service.

Related to !212 (closed)

Test Plan

Antoine, That's how i test manually:

bin/octocatalog-diff --octocatalog-diff-args --no-truncate-details --to staging moma                                Found host moma.softwareheritage.org
Cloning into '/tmp/swh-ocd.zu6cktWx/environments/production/data/private'...
done.
Cloning into '/tmp/swh-ocd.zu6cktWx/environments/staging/data/private'...
done.
*** Running octocatalog-diff on host moma.softwareheritage.org
I, [2020-04-08T16:52:57.346367 #30319]  INFO -- : Catalogs compiled for moma.softwareheritage.org
I, [2020-04-08T16:52:58.897509 #30319]  INFO -- : Diffs computed for moma.softwareheritage.org
diff origin/production/moma.softwareheritage.org current/moma.softwareheritage.org
*******************************************
  File[/etc/softwareheritage/web/web.yml] =>
   parameters =>
     content =>
      @@ -70,5 +70,7 @@
       client_config:
         sentry_dsn: swh::deploy::webapp::sentry_dsn
      -keycloak: '{"server_url"=>"", "realm_name"=>"SoftwareHeritage"}'
      +keycloak:
      +  server_url: ''
      +  realm_name: SoftwareHeritage
       allowed_hosts:
       - archive.softwareheritage.org
*******************************************
*** End octocatalog-diff on moma.softwareheritage.org

---

Migrated from D2982 (view on Phabricator)