Geo: add configuration for role and tracking database

Summary

From #8 (closed)

Add templates for the configuration of Geo, including related Cron-jobs

Configuration used

global:
  geo:
    enabled: false # boolean. Do we need this if we have `role`?
    role: # `primary`, `secondary`, nil only.
    # This is an optional identifier which Geo nodes can use to identify themselves.
    # For example, if external_url is the same for two secondaries, you must specify
    # a unique Geo node name for those secondaries.
    #
    # If it is blank, it defaults to external_url.
    nodeName:
    psql:
      host: # 
      port: # integer
      database: # string `gitlabhq_geo_producton`
      username: # string `gitlab_replicator`
      password:
        secret: # name
        key: # item key
      ssl:
        secret: # name
        clientKey: # item key
        clientCertificate: # item key 
        serverCA: # item key
  appConfig:
    cron_jobs:
      # geo_file_download_dispatch_worker:
      #  cron: "*/10 * * * *"
      # geo_repository_sync_worker:
      #   cron: "*/5 * * * *"
      # geo_prune_event_log_worker:
      #   cron: "*/5 * * * *"
      # geo_repository_verification_primary_batch_worker:
      #   cron: "*/5 * * * *"
      # geo_repository_verification_secondary_scheduler_worker:
      #   cron: "*/5 * * * *"
      # geo_migrated_local_files_clean_up_worker:
      #   cron: "15 */6 * * *"
      # ldap_sync_worker:
      #   cron: "30 1 * * *"
      # ldap_group_sync_worker:
      #   cron: "0 * * * *"
      # historical_data_worker:
      #   cron: "0 12 * * *" 

Dependencies

1. #1211 (closed) geo-logcursor container, gitlab-org/build/CNG!220 (merged)

cc @brodock