Introduce InstanceStatistics::Measurement model

What does this MR do?

This change introduces InstanceStatistics::Measurement model. Note that this change is not user facing.

We're planning to store object (record) counts periodically in this model to provide insights to the admins. See more info in the epics: &4147 (closed)

Migration:

Up:

== 20200827114902 CreateAnalyticsInstanceStatisticsMeasurements: migrating ====
-- create_table(:analytics_instance_statistics_measurements)
   -> 0.0125s
-- add_index(:analytics_instance_statistics_measurements, [:recorded_at, :identifier], {:unique=>true, :name=>"index_on_instance_statistics_recorded_at_and_identifier"})
   -> 0.0041s
== 20200827114902 CreateAnalyticsInstanceStatisticsMeasurements: migrated (0.0167s)

Down:

== 20200827114902 CreateAnalyticsInstanceStatisticsMeasurements: reverting ====
-- remove_index(:analytics_instance_statistics_measurements, {:name=>"index_on_instance_statistics_recorded_at_and_identifier"})
   -> 0.0015s
-- drop_table(:analytics_instance_statistics_measurements)
   -> 0.0012s
== 20200827114902 CreateAnalyticsInstanceStatisticsMeasurements: reverted (0.0054s)

The unique index will be used to UPSERT data.

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

Related #241673 (closed)