Add geo secondary web user usage ping

What does this MR do?

Adding a usage ping to count users of geo secondaries.

Relates to #273134 (closed)

Database Migration

Timing: 28.554s in #database-lab to create the index

Up output:

== 20201027210127 AddIndexToOauthAccessGrantsResourceOwnerId: migrating =======
-- transaction_open?()
   -> 0.0000s
-- index_exists?(:oauth_access_grants, [:resource_owner_id, :application_id, :created_at], {:name=>"index_oauth_access_grants_on_resource_owner_id", :algorithm=>:concurrently})
   -> 0.0020s
-- execute("SET statement_timeout TO 0")
   -> 0.0004s
-- add_index(:oauth_access_grants, [:resource_owner_id, :application_id, :created_at], {:name=>"index_oauth_access_grants_on_resource_owner_id", :algorithm=>:concurrently})
   -> 0.0033s
-- execute("RESET ALL")
   -> 0.0004s
== 20201027210127 AddIndexToOauthAccessGrantsResourceOwnerId: migrated (0.0070s) 

Down output:

== 20201027210127 AddIndexToOauthAccessGrantsResourceOwnerId: reverting =======
-- transaction_open?()
   -> 0.0000s
-- indexes(:oauth_access_grants)
   -> 0.0026s
-- execute("SET statement_timeout TO 0")
   -> 0.0004s
-- remove_index(:oauth_access_grants, {:algorithm=>:concurrently, :name=>"index_oauth_access_grants_on_resource_owner_id"})
   -> 0.0020s
-- execute("RESET ALL")
   -> 0.0004s
== 20201027210127 AddIndexToOauthAccessGrantsResourceOwnerId: reverted (0.0061s) 

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team