Track Cilium installation status through the cluster applications project

Problem to solve

Now that #35672 (closed) is implemented we have a way to get a installation state for Cilium through the helm ls based artifact. Getting this state is necessary for a more performant metrics collection: #211532 (closed)

Intended users

User experience goal

Proposal

• Create a new cluster application DB table where we can store installation state. List of current models is here: https://gitlab.com/gitlab-org/gitlab/-/tree/8ec141d839ff7d6aa1fee5ccd7d8d3083447e10b/app/models/clusters/applications
• Update related service to sync Cilium state with a new table: https://gitlab.com/gitlab-org/gitlab/-/blob/8ec141d839ff7d6aa1fee5ccd7d8d3083447e10b/app/services/clusters/parse_cluster_applications_artifact_service.rb

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references