Add clusters_applications_cilium DB table

What does this MR do?

Add a new table for the Cilium cluster application. This table will be used in #220419 (closed) to track Cilium's installation state through the cluster applications project.

Migration output:

[ap4y@ap4y-laptop gitlab]$ bin/rails db:rollback
== 20200615234047 CreateClustersApplicationsCilium: reverting =================
-- drop_table(:clusters_applications_cilium)
   -> 0.0012s
== 20200615234047 CreateClustersApplicationsCilium: reverted (0.0021s) ========

[ap4y@ap4y-laptop gitlab]$ bin/rails db:migrate
== 20200615234047 CreateClustersApplicationsCilium: migrating =================
-- create_table(:clusters_applications_cilium)
   -> 0.0144s
== 20200615234047 CreateClustersApplicationsCilium: migrated (0.0145s) ========

Screenshots

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