Add tables to support geo secondary usage data

What does this MR do?

Adds tables to allow for usage data collection on secondaries that can be re-transmitted to primaries. This is only adding the database table. Future work to populate the table will continue in a separate merge request.

Related to #298781 (closed)

Database

This table will be created in the geo tracking database since the primary database is read only on secondaries. This allows us to store the data we'll collect in the background for later transmission as a part of the geo node status.

Migrate:

== 20210208175408 CreateGeoSecondaryUsageData: migrating ======================
-- create_table(:secondary_usage_data)
   -> 0.0048s
== 20210208175408 CreateGeoSecondaryUsageData: migrated (0.0048s) =============

Rollback:

== 20210208175408 CreateGeoSecondaryUsageData: reverting ======================
-- drop_table(:secondary_usage_data)
   -> 0.0053s
== 20210208175408 CreateGeoSecondaryUsageData: reverted (0.0068s) =============

Screenshots (strongly suggested)

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